Test case management
TSMC keeps cases the way you keep code: in git, reviewed and versioned. It tells you what to run for the changes of a pull request, and keeps the case base from filling up with duplicates and dead checks.
The usual — a suite tree, steps, runs, reports — is all there. What differs is how it fits into the team’s work.
Cases are Markdown files in the product’s repository. A case edit goes into the same pull request as the code, gets reviewed and reaches the server in one atomic command. A conflict with an edit on the server is never lost.
tsmc pull -d qa/cases
tsmc push -d qa/cases --dry-runCases and suites know which code they check. From a list of changed files TSMC ranks cases and explains why each was picked — and lists the files no case covers.
tsmc impact -p SHOP --base origin/main
--create-run "PR 42"Likely duplicates and cases not run for long, never failing or flipping between passed and failed — on one tab. A duplicate is compared side by side and closed in one click.
Learn more →The real interface on demo data: an online shop with half a year of run history.
And nothing extra: what a tester, a QA lead and CI need every day.
Steps "action → expected result", formatting, shared steps, parameters with iterations. Every edit is a new version with its author.
Cases picked by tree and filters, hotkeys, step statuses, assignees, rerunning a closed run.
Runs by sprint and release, a milestone report: each case by its latest result and what fails now.
A dashboard for a period, a run report compared with the previous run, PDF printing and a link without sign-in.
JUnit XML from pytest, Jest, Playwright, Go and more. Matched to cases by key, attachments from the report.
GitHub Issues, Jira and YouTrack: a bug from a failed case in one click, statuses of linked issues in the run.
Import from TestRail, Qase and any CSV with a preview. Export to CSV and Excel.
Four roles, project API tokens, an audit log: who changed what, and from where.
The CLI is one file with no dependencies: it is in the Docker image and builds from the repository. A project token and two lines in the pipeline.
A JUnit report is matched to cases; screenshots from the report are attached to the results.
tsmc junit upload build/test-results/*.xml \
-p SHOP -r "Nightly $BUILD" --fail-on-failedA run of the cases the branch’s changes affect — with the reasons.
tsmc impact -p SHOP --base origin/main \
--create-run "PR $PR_NUMBER"TSMC needs no cloud service: the server is up in minutes and needs almost no care.
Node.js or a Docker image; the database is one SQLite file, attachments next to it on disk.
A consistent snapshot of the database and attachments without stopping the server, checks and restore.
Tested on 20,000 cases and 500 runs: the list and search take tens of milliseconds.
You can run TSMC on your own server today. A cloud version and commercial terms are in the works.
$0forever
Everything TSMC does, on your server.
—
TSMC without a server of your own: we host, update and back it up.
On request
For teams that need help with adoption and support.
Prices are preliminary and may change.