Organize test suites and requirements, execute frozen test runs, record step results and defects, compare builds and export a complete release evidence bundle. A local browser workspace for manual software QA.
Frozen run snapshotsStep results & traceabilityHTML reports & evidence ZIP
☷ → ✓CASES · RUNS · RELEASE EVIDENCE
From an idea to a usable result
Organize your case library into suites. Add preconditions, ordered actions, expected results, priorities, tags and requirement links.
Create a run for a build and scope. Case and requirement text is frozen into that run so later library edits do not rewrite old evidence.
Record per-step results, actual behavior and linked defects. Use quick overall results when appropriate, then complete and lock the run.
Inspect requirement coverage, compare runs and review release checks. Export the report, results CSV, test plan, project or complete evidence ZIP.
What to expect
Local manual QA, not an automated browser runner or hosted issue tracker. Up to 500 library cases, 40 steps per case, 50 suites, 300 requirements, 500 defects and 30 runs, with 3,000 total case snapshots. Projects: 8 MiB. No binary evidence attachments or multi-user synchronization. Release checks summarize entered records; they do not certify software quality.
Processing happens in your browser. Save a project before closing the page. Optional drafts stay in this browser. Public pages include advertising and optional analytics under our privacy policy.
Using Test Case & Release QA Workbench
Organize test suites and requirements, execute frozen test runs, record step results and defects, compare builds and export a complete release evidence bundle. A local browser workspace for manual software QA.
Organize your case library into suites. Add preconditions, ordered actions, expected results, priorities, tags and requirement links.
Create a run for a build and scope. Case and requirement text is frozen into that run so later library edits do not rewrite old evidence.
Record per-step results, actual behavior and linked defects. Use quick overall results when appropriate, then complete and lock the run.
Inspect requirement coverage, compare runs and review release checks. Export the report, results CSV, test plan, project or complete evidence ZIP.
Example
Organize your case library into suites. Add preconditions, ordered actions, expected results, priorities, tags and requirement links.
Questions & answers
Will editing a case change an older test run?
No. Each run stores its own case and requirement snapshots. Library edits affect future runs. Completed run results are locked in the UI until you explicitly reopen the run.
How is pass rate calculated?
Passed divided by passed plus failed. Blocked, skipped and not-run cases are excluded from that denominator and shown separately. Release checks separately require no blocked or not-run cases.
Can I import test cases from a spreadsheet?
Export CSV with code,title,action,expected headers. Optional suite,priority and preconditions columns are supported. Repeated case codes append ordered steps. Import starts a new project.
Can I share a report without this tool?
Yes. HTML reports include static results, steps, actual notes, requirement coverage and release checks. Open them directly and print to PDF. The ZIP bundles the report, CSV, Markdown plan and editable project.
