Two Runs. One Command. The Actual Difference.
A passing run and a failing run of the same suite aren't identical — something changed. testsprite test diff <runId1> <runId2> shows you exactly what, instead of leaving you to compare logs by hand.
Diff Any Two Runs, Any Two Environments
Save What You Broke
testsprite test diff <runId1> <runId2> pinpoints exactly which tests flipped between two runs — no more scrolling through two separate reports side by side.
Understand What You Want
Diff a run from before a deploy against one from after it, and the change surface is exactly what your deploy touched — nothing you have to guess at.
Validate What You Have
Diffs go deeper than pass/fail — they cover the request/response and DOM-level detail behind each test, where available.
Suggest What You Need
Pair a diff with testsprite test failure get on whichever test flipped to bad, and you've got the full story: what changed, and why it broke.
$ testsprite test diff run_9f21 run_9f30
TC_checkout_promo passed → failed
POST /orders 201 → 500
rootCause: "promo code not revalidated server-side"
TC_login_success passed → passed (no change)
TC_search_results passed → passed (no change)
Stop Comparing Logs By Hand
Two runs of the same suite, minutes or months apart — the diff is the same command either way, and it's built to answer one question: what actually changed?
Built for Debugging Regressions Fast
Compare Across Deploys
Run a suite before and after a release, diff the two, and know immediately if the release is clean.
Compare Across Time
testsprite test result <testId> --history shows a test's own run history if you want the trend, not just two points.
Free Community Version
Offers a free community version, making us accessible to everyone.
Pairs With Flaky Scoring
Use test flaky first to confirm a change is real, then test diff to see exactly what it was.
Trusted By Businesses Worldwide
"TestSprite offers rich test case generation, clear structure, and easy-to-read code. It also supports simple online debugging with the ability to quickly expand by generating new test cases."
"TestSprite's automation helps us reduce tons of manual work. The developers can easily catch and resolve bugs earlier in the development process."
FAQ
What does testsprite test diff actually compare?
Two runs of the same or related test suite — which tests flipped pass/fail, and the request/response or DOM-level detail behind that change where available.
Can I diff a run from last week against one from today?
Yes — any two run IDs, regardless of how far apart they happened.
How is this different from just reading two test reports?
It surfaces the delta directly instead of asking you to hold both reports in your head and spot the difference yourself.
Can I see a single test's history over many runs, not just two?
Yes — testsprite test result <testId> --history shows the trend across every run of that test.
Does this replace test flaky?
No — they pair well together. Use test flaky to confirm a failure is real, then test diff to see exactly what changed.