Test-case change history
See a chronological record of test-case edits, step changes, test data changes, and other recorded actions.
Review test-case change history, attach execution evidence, and keep requirement and defect discussions with their records.
The result alone rarely tells the whole story. The application keeps supporting files, changes, and comments near the test and issue they describe, subject to workspace permissions.
See a chronological record of test-case edits, step changes, test data changes, and other recorded actions.
Upload and review files that support a test run or an individual test-case execution.
Keep supporting documents and files with the requirement they clarify.
Discuss requirements and defects in their detail views so the conversation stays connected to the record.
Preserve the context a team needs to reproduce, review, and resolve quality issues.
Start with your next set of requirements or talk with the Quality At AI team.