Give every case a clear home
Organize work by Project, Test Group, and nested Section, with steps, expected results, priority, owner, tags, notes, and attachments.
02 / Design
Keep test knowledge current without losing release history
Build reusable Test Cases, preserve every meaningful change, and run point-in-time snapshots that show exactly what the team tested.
The source library can keep improving while every Test Run preserves the version that produced the result.
StructuredTest Groups and nested Sections
Versionedcases and shared templates
Snapshotevidence for every Test Run
Knowledge that survives change
Improve the test library without changing the past.
Structure reusable coverage for the next release while point-in-time Run snapshots preserve exactly what the team executed before.
Reuse knowledge without copy-and-paste
Link shared text or ordered step blocks to multiple cases and update future rendering from one controlled Project Template.
Run the right version every time
Create execution snapshots, assign work, filter the run, record result history, batch-update cases, and share a direct Run Case view.
Move existing suites with confidence
Map and preview CSV or XLSX imports, export the active suite to XLSX, and restore archived or previous case versions when needed.
Author once, snapshot deliberately
Separate living test design from fixed release evidence.
Cases and templates continue to evolve in the source library; each Test Run holds a stable execution copy with its own assignments and result history.
Structure the product
Create Test Groups and nested Sections manually or turn a Mind Map branch into the starting hierarchy.
Build reusable coverage
Write cases, apply templates and tags, and retain version history as the product changes.
Execute a fixed snapshot
Add cases to a Test Run and record Not Run, Passed, Failed, Blocked, or Skipped results without rewriting the source cases.
A defensible release record
Trust both the test library and the release record
Teams keep a maintainable source of testing knowledge and a defensible record of what was actually executed for each release and environment.
Review plans and evaluation