Environments
The stand a run happens on: dev, test, pre-prod. A result is always tied to its environment.
Test plans and runs
A plan gathers cases from different suites and keeps assignments for future runs. The run wizard takes you step by step: statuses, comments, attachments and execution time.
Test plans
Cases from different suites come together in one plan. Assignments are kept, so the next run starts from a ready plan rather than an empty list.
- Cases from different suites in one plan
- Assignments are kept for future runs
- One plan runs across environments and configurations
Runs and the run wizard
The wizard takes you through cases step by step. Each step gets a status, and the result is recorded together with the evidence.
- Statuses per step and per case
- Comments and attachments: screenshots, logs
- Execution time for every case
- A YaGA defect from a failed case in one click
Assignees
Work is split up inside the run, so you no longer need a separate “who takes what” spreadsheet.
- Assigning a case in a run to a tester
- Statistics per assignee
- Notifications on assignments and run statuses
Environments, configurations and releases
Configurations
Browsers, operating systems, versions: one suite of cases runs under different conditions.
Releases and sprints
Runs are tied to milestones, so release readiness is visible at once.
Automated tests from GitLab
A pipeline starts from the run, and automated test results come back into its card.
Start your first run
Build a plan from existing cases, assign testers and walk it through end to end. The Pro trial needs no card and is long enough to run a real release.
30 minutes online with a CommIT expert: we walk you through the product and answer questions about your process