Separate intended changes from regressions
Each observed change is marked intended or not, so the report does not confuse a planned redesign with an accidental visual break.
Free MVP QA tool
UIRegression
Log what a screen looked like before a deployment and what changed after, and get a report separating intended changes from likely regressions.
- Calculated instantly from your inputs
- No signup or data submission
- A focused next step for MVP planning
Your entries remain in this browser session and are not sent to MVPHub.
Your inputs
Compare a screen before and after deployment
Enter one observed change per line as Change observed | intended (yes/no) | severity (low/medium/high). List every visual difference you noticed after the deployment.
Your calculated result
Your result
0/100
Planning score
Recommended next actions
How it works
Weight regressions by severity
Unintended changes are rated by severity, so a misaligned footer link and an overlapping button do not get equal urgency.
Prioritize the highest-severity regressions
The report ranks unintended changes by severity so the most visible or functionally damaging issues get fixed first.
Frequently asked questions
Does this automatically capture before/after screenshots?
No — you log what you observed after visually comparing the two states yourself. There is no automated screenshot capture.
What if I am not sure whether a change was intended?
Mark it "no" and flag it for the team — treating an uncertain change as a possible regression is safer than assuming it was planned.
Should low-severity regressions be fixed immediately?
Not necessarily — use the severity ranking to decide whether it blocks the release or can go into a follow-up fix.
How is this different from DesignDiff?
DesignDiff compares two design versions before implementation; UIRegression compares the live site before and after a deployment to catch unintended implementation changes.
How we compare
| Capability | MVPHub | Manually eyeballing the site after each release | Percy or Chromatic automated visual regression |
|---|---|---|---|
| Separates intended changes from regressions explicitly | ✓ | × | — |
| Ranks regressions by severity automatically | ✓ | × | × |
| Automated screenshot diffing in CI | × | × | ✓ |
| No account, paste and get a report instantly | ✓ | ✓ | × |
MVPHub structures a manual post-deployment check into a prioritized report. Percy and Chromatic catch regressions automatically in CI but require setup and ongoing maintenance.