How-to Guide
Edit a test case
Update steps, expected results, or metadata for an existing case.
Objective
Update steps, expected results, or metadata for an existing case.
Prerequisites
- Case exists in test library
Procedure
Locate case
Open Tests library and filter or search for the case.
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.
Edit fields
Update steps, expected output, priority, or platform.
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.
Save changes
Save and verify updated case appears in project context.
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
Case reflects corrected validation logic.
Was this page helpful?