Environments
The stand a run happens on: dev, staging, pre-production. A result is always tied to its environment.
Test plans and test runs
A plan groups cases by release, feature or priority and gets reused next sprint. A run shows statuses, comments, attachments and owners.
Test plans
A plan collects cases for one specific job: a release, a feature or a priority level. The next sprint starts from a ready plan instead of an empty list.
- Picking cases by suite, tag or priority
- A plan is reused in the next sprint
- One plan unfolds into several runs
The run and its results
A run shows what is already done, what failed and where work stopped. Every result is recorded together with its evidence.
- Statuses: passed, failed, blocked, skipped
- Comments and attachments with screenshots and logs
- A link to a tracker task right on the case inside the run
- Execution time and the history of attempts
Owners
Work is distributed inside the run, so the separate spreadsheet of who takes what is no longer needed.
- Assigning an owner to a case inside a run
- Workload per person and their contribution are visible
- A new member can be invited to the project by link
Environments, configurations and releases
Configurations
Browser, platform, version. One plan runs across a matrix of configurations, not a single row.
Releases
Runs are attached to a release, so readiness to ship is visible at a glance.
Run your first suite
Build a plan from existing cases, assign owners and walk it through. That takes a day, not a quarter of rollout.