Retain the executed revision
Later edits do not rewrite the Test Case definition attached to recorded execution.
Native test management
Test the requirement. Keep the evidence.
Manage Test Cases and Test Runs beside requirements and delivery work. Keep execution results connected to the exact instructions that were tested.
Organize the QA library.
Suites and nested sections organize your cases. Give each case preconditions, steps and an observable expected result; use ownership, templates and custom fields to keep authoring consistent.
Run tests and keep the evidence.
Search and select suites or cases, create a Test Run, and record results with notes. Track Pending, Passed, Failed, Blocked and Skipped outcomes.
Know which instructions were executed.
Compare and restore
Inspect changes between definitions. Restoring creates a new revision and preserves the history.
Turn evidence into work
Create a linked defect from a failed or blocked result, keeping the original evidence accessible.
Bring CI results into the same record.
Submit JUnit reports through the scoped integration API. Results match existing Test Cases by supported ID/title rules; ambiguous and unmatched entries receive diagnostics. Yetea consumes the report rather than running tests itself.
GitHub Actions and GitLab CI examples describe report submission, not native repository integrations with both providers.
Keep QA portable.
Compatible QA CSV/XML imports and exports help you move a library. Confirm the format with support before migrating.
Ask about import compatibilityA few useful distinctions.
Can I record tests without a linked task?
Yes. Test Runs manage execution in their own right. Linking a Test Case to a task adds a verification signal to that task.
What happens when a case changes after a run?
Executed revisions remain in history. Linked task evidence can become stale until the changed case is tested again.
Can I import any CSV or XML file?
No. Files must match supported QA schemas. A generic traceability spreadsheet is not a native QA import file.
Connect the reason to the result.
Ship confidently. Breathe easy.
Make your next release
easier to account for.
Keep the requirement, the work, and the test evidence together. Start with one real project.