Shared steps
Recurring steps, such as signing in, live in one place instead of being copied into every case.
Test cases and repository
Nested suites, steps with data and expected results, tags and priorities, shared steps and custom fields. A case enters the repository only after review.
Case repository
Cases live in nested suites, not a flat list: a large base stays visible as a whole and is easy to work through branch by branch.
- Nested suites of any depth
- Steps with test data and expected results
- Tags and priorities, with search and filters on them
- Bulk editing and copying between projects
Git-style review
A new case or an edit goes to review. Reviewers see a line-by-line diff, comment, approve and merge. A case enters the repository only after approval.
- A line-by-line diff of every edit
- Inline comments before approval
- A required number of approvals and no self-merge
- Case change history
Shared steps, custom fields and test data
Custom fields
Case attributes of 5 types for your process: component, layer, requirement ID.
Test data store
Logins, JSON, cards and files are kept apart from cases, with change history and an expiry date. Expired records are archived automatically.
Import and export
Import from TestRail, Zephyr, Xray, Qase, TestLink, CSV and Excel. Export in 6 formats.
Related sections
Bring your base over and see
Import cases from your current system or generate them with AI from a ticket. For a large base we help out: the trial import runs on your own project.
30 minutes online with a CommIT expert: we walk you through the product and answer questions about your process