TestDefinitionAgent

To define verifiable test cases for software components, generate structured TEST Cards specifying objectives, required artifacts, verification procedures, and negative test scenarios prior to code execution. This evidence gating ensures tests align with quality gates and TDD methodologies.

Evidence gating in test definition is a mechanism that prevents execution plans from proceeding until structured test definitions and their required evidence are complete. It acts as a quality assurance gate to guarantee verifiable proof exists before software execution begins.

You structure test objectives and verification procedures for TDD by creating TEST Cards that explicitly outline what constitutes a successful test, the required artifacts, and the verification methods needed. This ensures quality from the outset of feature development.

Yes, you can block execution plans until test definitions are complete by applying evidence gating. This feature ensures that no execution plan proceeds unless structured TEST Cards specifying objectives, artifacts, and verification procedures are fully defined.

Negative test scenarios are failure cases defined within structured TEST Cards to verify how software components handle invalid inputs or errors. You specify them during test definition to ensure comprehensive verification procedures and evidence requirements cover edge cases.

You need to define test cases as explicit requirements before coding when adopting TDD methodologies or requiring strict quality assurance. Defining tests first acts as a crucial gate for verifiable evidence, ensuring all execution plans meet predefined quality gates.