Custom fields
A project adds its own fields to a case: component, layer, requirement number. Moving a large base over is hard without them.
Test cases and repository
Cases live in a suite hierarchy with steps, preconditions, priorities and tags. Bulk edit them, copy between projects, review before a run.
Repository and suite hierarchy
Cases sit in a tree of suites of any depth rather than a flat list, so a large base stays readable and can be worked branch by branch.
- Steps with an action and an expected result
- Preconditions on a case and shared preconditions for the project
- Priorities, tags and search across them
- Copying between projects and bulk editing
Review and sign-off
A case is checked before a release is run against it. Disputed wording is settled in comments rather than in a chat thread.
- Sending a case for review with a visible review status
- Inline comments and discussion until the case is approved
- Change history: what changed and when
Fields, tags and the archive
Tags
Navigation across the whole base: smoke, regression, payments. A tag drives both a selection and a test plan.
Case links
A case links to another case, and inside a run it carries a link to a task in your tracker. Traceability is not lost.
Archive
An outdated case goes to the archive instead of being deleted: its run history stays in place.
Related sections
- AI generationA task description goes in, structured cases come out. The edits stay with you.
- Test plans and runsA plan collects the cases, a run records the result. Environments, configurations, releases.
- Analytics and reportsDashboards, widgets, the run report and a public link to it with no sign-in.
Move your base over and look
Import from CSV and Excel, and from TestRail, Zephyr and Xray exports. We help with field mapping at the start.