Most reviews praise TestSprite for hands-off automation that writes, runs, and fixes tests, speeding delivery and catching issues early. Users highlight easy setup, natural-language workflows, and strong coverage for both frontend and backend, often noting big time savings and smoother QA cycles. Teams value reliability and clear reports, though some ask for richer reporting, better scaling, and trials for paid plans. A few off-topic comments mention “smooth animation,” but the consistent theme is faster iteration, less manual effort, and a helpful boost to developer productivity.
What's the biggest difference between 3.0 and 4.0?
Congrats @jiao_yunhao . I am founder of the agentic API platform Flaq AI: https://flaq.ai/. Test Sprite is so amazing for the test project. We will try it. Good luck to your team!
Does it cover backend APIs and data as well, or is it mostly UI testing?
Does this make sense for a team that already has a QA engineer, or is it mainly for teams that don't?
when the PRD and the app disagree, which one does it treat as right?
Rebuilding the product as a brand-new agent after 150,000+ developers built on the old one takes guts. Congrats on 4.0.
This is the part of AI coding I feel the most — my agent fixes one thing and quietly breaks another. The loop where the testing agent finds the bug, suggests the fix and retests it is what I'd actually trust before merging. Curious how it holds up on a second run of the same suite — do the tests stay stable so a regression shows up as a real diff, or are they regenerated each time?