Feature · Insights · Regression
What broke
since?
The question after every deploy. QAMind diffs this run against the last one and names the cases that flipped. Toggle the filter.
passed last run → failed this run
Pass to fail transitions are the signal; everything else is noise the filter removes.
In the product
How it actually works.
Build regression suites
Pick cases across projects and tag them — smoke, regression, critical-path, e2e, api, ui, or your own labels. These are the flows that must not break.
Run them on demand
Point the focused run panel at a project and suite and execute. Rerunning a regression suite is deliberately cheap and boring.
Read the diff
Cases that passed last run and failed this one are the regressions — flagged loudly, separated from the long-standing failures everyone already knows about.
See these steps on screen
coming soonA guided video of this exact flow is being recorded — it will live right here.
Spec sheet