create-tests

Generating test cases from an approved SRS requires mapping each Acceptance Criterion to a traceable Test Case. This process creates a complete Test Concept and individual test files idempotently, ensuring deterministic artifact generation directly from the settled specification.

Requirements drift detection cross-checks Acceptance Criteria against the upstream Elicitation Document to identify mismatched wording or missing upstream data. It raises severity-flagged Open Questions to alert teams when the specification diverges from elicited requirements.

Enforcing traceability between acceptance criteria and test cases involves creating a strict one-to-one mapping where each AC ID generates a unique TC ID. This prevents ID reuse and ensures every test artifact links directly back to its originating requirement.

Yes, you need an accepted SRS status before generating QA review gates. The test generation stops immediately unless the SRS file exists and has an Accepted status, ensuring tests are only derived from a settled and approved specification.

Test types and levels are assigned using deterministic heuristics based on the Acceptance Criterion wording. The system automatically categorizes tests as Functional, Performance, or Security types and includes an AI-assignment confirmation note for audit transparency.

No, you cannot edit test cases after they have been accepted or rejected. The system protects these artifacts from regeneration edits by making them immutable and only appends audit notes to maintain historical integrity and compliance.