How-to Guide
Review generated test cases
Human validation of AI-generated cases before execution.
Objective
Human validation of AI-generated cases before execution.
Prerequisites
- Generated scenarios exist
Procedure
Open test cases step
Navigate to the project wizard test cases step or test library.
Navigation: Quality → Tests, Coverage, or Test Health. Link work to a project when validating generation or traceability.
Verification: Confirm organization and team context in the Console header before making changes.
Review steps and expectations
Verify steps JSON, expected outcomes, and priority.
Navigation: Quality → Tests, Coverage, or Test Health. Link work to a project when validating generation or traceability.
Verification: Note project, run, or agent IDs if you may need support escalation.
Edit or reject
Correct inaccuracies before approving for execution.
Navigation: Quality → Tests, Coverage, or Test Health. Link work to a project when validating generation or traceability.
Verification: Confirm UI state matches your runbook. Retry once on transient errors before opening a ticket.
Policy: Human review of AI-generated tests is required before release-critical reliance.
Verification checklist
- Confirm expected UI state or API response after each critical step
- Document run ID, project ID, or agent ID for support escalation if needed
- Notify stakeholders if the workflow affects release gates or production validation
Expected result
Approved cases are ready for runs or suite organization.
Was this page helpful?