Every Test Run Leaves Evidence Behind.
A green checkmark with nothing behind it is a claim, not proof. testsprite test artifact get <runId> pulls the actual evidence — screenshots, DOM snapshots, request/response logs — for any run, so you can check the work, not just the verdict.
Every Run, On the Record
Save What You Broke
testsprite test artifact get <runId> pulls the full evidence bundle for a run — not just the pass/fail line, the actual screenshots and logs behind it.
Understand What You Want
testsprite test result <testId> --history shows how a test has behaved over every run, not just the most recent one.
Validate What You Have
Evidence is captured from the real execution against your live environment — the same artifacts a person debugging the failure by hand would want.
Suggest What You Need
Pair the artifact with test failure get on a failing run, and you've got both the raw evidence and the root-cause hypothesis in one place.
$ testsprite test run --all --project prj_8f2a --wait --output json ✓ TC_checkout_flow passed run_9f21 $ testsprite test artifact get run_9f21 --out ./evidence ✓ Saved screenshots, DOM snapshot, request logs to ./evidence $ testsprite test result TC_checkout_flow --history run_9c10 passed run_9e88 passed run_9f21 passed
Proof, Not Just a Pass/Fail Line
Anyone can claim a test passed. An audit trail is what lets someone else check that claim without re-running the test themselves.
Built for When Someone Asks "Are You Sure?"
Evidence on Every Run
Artifacts are captured automatically — you don't have to remember to turn on recording before a run that matters.
History, Not Just a Snapshot
test result --history shows the trend, useful for spotting a slow regression that a single run wouldn't reveal.
Free Community Version
Offers a free community version, making us accessible to everyone.
Pairs With Diffing
Combine artifacts with test diff to see the evidence for exactly what changed between two runs.
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's actually in a run's artifact bundle?
Screenshots, DOM snapshots, and request/response logs from the real execution — the same evidence a person debugging the failure by hand would collect.
Do I have to configure anything to get artifacts?
No — they're captured as part of the run. testsprite test artifact get <runId> retrieves them after the fact.
Can I see how a test has performed over time, not just its latest run?
Yes — testsprite test result <testId> --history shows every run of that test, not just the most recent one.
Why does this matter if the test already reported pass or fail?
Because a status line is a claim — the artifact is what lets you or a teammate verify that claim instead of taking it on faith.
Does this work for tests I uploaded myself?
Yes — artifact capture and history work the same whether the test was generated or uploaded with test code put.