Quash
A mobile QA agent that runs tests without scripts
416 followers
A mobile QA agent that runs tests without scripts
416 followers
Quash is an intent-driven mobile testing tool that lets you write and run tests in plain language instead of scripts. You can run tests on real devices, cloud devices or local emulators. Quash adapts when the UI changes using built-in self healing, understands app behavior across builds, supports backend validations, reusable test data, test suites and running tests in parallel. Every run generates detailed execution reports with step level intent, actions and screenshots.
Free Options
Launch Team / Built With
Quash
Hey PH! I’m Prakhar, co-founder at Quash 👋
Teams ship mobile apps faster than ever today. When a human tests an app, they adapt constantly. They notice changes, recover from small failures and move forward. Most testing tools don’t work that way. They expect apps to behave predictably while everything else in product development is optimized for change.
What felt missing was intent and context. Humans don’t test apps by replaying scripts. They carry context from one screen to the next and adjust based on what they see. We wanted testing to work the same way. That shift pushed us to rebuild Quash around agentic execution.
Today, Quash acts as a mobile use agent. You describe what you want to test in plain language and the agent handles tapping, scrolling, navigation, form handling and backend validations while keeping context intact. It adapts when the UI changes and runs on real devices, cloud devices or local emulators, one at a time or in parallel.
We launched our GA version recently and hosted a small community event in Bangalore. Putting Quash in front of QAs, developers and PMs helped sharpen the product and the narrative. The feedback pushed us toward clearer execution, context aware test suites and reports that developers and PMs can actually use without us explaining every step.
Visibility matters a lot to us. Every run shows step level intent, actions taken, screenshots, device recordings and backend validations so you always know what happened and why.
This is the version of Quash that finally feels like it can stand on its own. If mobile test automation has ever felt brittle or harder than it should be, we’d love for you to check out the playground on our site, try it yourself, and share your feedback.
Try it here: https://quashbugs.com/
Big thanks to @zaczuo for hunting us 🙌
Quash
We have Quash built to make mobile app testing as seamless as using ChatGPT to make life easy for Devs and PMs everywhere. It's free to use too.
@zaczuo @pr_khar Does Quash maintain state when a test flow crosses app boundaries... like a deep link that kicks to a browser, redirects, and lands back on a different screen? That handoff is where most scriptless tools lose track. Plain-English step definitions decoupled from selectors is smart because UI churn stops breaking everything. But intent alone doesn't solve the state problem when the OS itself is the middleman between apps.
Quash
@piroune_balachandran So yeah, Quash does maintain state across any number of apps in a single session. We use the term 'Mobile-use' cause that's what explains it the best, quash directly interacts with the device OS, not just the app, and there's no use of selectors at all - it's more vision based.
Agnes AI
Hmmm will QA be replaced soon? Quash really surprises me with no scripts running! nice tool!
Quash
@cruise_chen Thanks Cruise! Appreciate your support.
Quash
Launched Quash today! Built as a dev for devs to turn plain language into reliable mobile tests and get rich bug insights without scripts. Excited for your feedback and ideas! 🙌
Quash
Hi PH!
As developers, we know exactly how painful mobile testing is with the flaky scripts, the broken UI selectors, and the constant maintenance. It’s a massive bottleneck.
We built Quash to solve our own frustrations. It’s a haven for testers where you write in plain language and let our self-healing AI handle the rest.
We’re here to connect and learn. What’s the biggest "break the screen" moment you've had with mobile QA? Throw it at our agent and see it handle with ease and comfort.
Quash
Super excited to share Quash with everyone today. Mobile testing has been a headache for a long time—hopefully, this makes it a little less painful for you all. Let us know if you have any questions!
Quash
So happy to be part of this team! 🚀 We’ve put a lot of work into making this a reality, and I’m personally excited to see how you all use it.
The self-healing angle is what caught my eye. We've had the same problem on the API side -- test suites that break every time a response schema changes slightly. Plain language intent over rigid assertions makes a lot more sense for mobile where the UI shifts constantly.
How deep does the backend validation go? Can it check things like response status codes and payload structure, or is it mostly focused on the UI layer?
Quash