edge-case-tests

To generate edge-case tests for multi-agent ticket workflows, you can use a skill that proposes adversarial, invariant, and boundary-case test ideas. It outputs deterministic artifacts to ensure coverage for determinism, ordering, recovery, and safety across agents.

Adversarial and boundary-case tests in acceptance testing are scenarios designed to probe the limits of ticket criteria. They propose invariant checks and boundary conditions to ensure multi-agent systems handle safety, recovery, and ordering correctly.

Yes, you can propose invariant tests without modifying production code. The skill specifically operates under guardrails that avoid editing production code, outputting review-ready proposals instead of materializing the tests directly.

The best way to strengthen ticket acceptance coverage is to propose adversarial, invariant, and boundary-case tests. This approach ensures multi-agent workflows have deterministic coverage for ordering, recovery, and safety without altering production code.

No, the edge-case-tests skill does not write or execute test code. It operates under strict guardrails to avoid materializing tests or editing production code, strictly producing a review-ready proposal artifact.

To extend acceptance criteria with boundary-case test proposals, apply a skill that generates adversarial and invariant test ideas. It creates a deterministic proposal artifact to complement existing acceptance tests for multi-agent ticket workflows.