Launching today

QApilot
3x Mobile Automation. Same QE Team.
132 followers
3x Mobile Automation. Same QE Team.
132 followers
CoWork turns existing test cases into executable mobile automation with AI planning, human-approved replanning, and real-device execution on iOS, Android, and Flutter.
Interactive







Payment Required
Launch Team / Built With



QApilot
Hey everyone, Charan from QApilot here.
Every QA team knows what they want to test. "Log in, add an item to the cart, check the order confirmation." Saying it takes ten seconds. Then the team spends six months turning that sentence into something a machine will run: step definitions, selectors, automation glue, flaky scripts that break on every UI change.
The intent was never the hard part. The execution layer was the tax.
CoWork takes your existing natural-language or BDD test cases, converts them into structured BDD/Gherkin context, builds an execution plan, and runs the test on a real mobile device.
When the app behaves differently, like a changed label, unexpected popup, or interrupted flow, CoWork replans and asks for human approval before moving ahead. When it needs input, like an OTP, it pauses instead of guessing. If it can’t proceed, it fails honestly instead of faking a pass.
Who it’s for: QA leaders, SDETs, mobile engineering teams, and product teams with existing test cases but low execution coverage before releases.
Common use cases: Regression testing, Release readiness, checkout/login flows, OTP-heavy journeys, app flows that break often, and teams trying to reduce manual execution without rewriting everything from scratch.
What makes CoWork different is the balance: AI execution where it can move fast, human control where judgment matters.
If you run mobile tests, I’d genuinely love your take. Try it here: https://qapilot.io/product/cowork
Thanks for being here for the launch. I’ll be in the thread all day reading every comment.
-- Charan Tej, Product Guy @QApilot's CoWork
the six-months-to-automate part is real. my team gave up automating our iOS app last year because every release broke the selectors. went back to manual regression and shipped slower for 6 months.
what i'd want to know about qapilot: when an iOS update changes the entire navigation hierarchy, does the AI re-plan or does it break the same way our selectors did? that's the test for whether this actually saves a QA team or just shifts the breakage to a different layer.
QApilot
@thenameisarian That's a real pain, especially for fast moving mobile app teams. We built CoWork's planning module such that it intelligently replans, finds new correct selectors, and executes the tests. The QA can choose to update these selectors as default for the future automation runs too. Essentially saving QA's time and effort to focus on test intent rather than maintenance.
The selector breakage problem is real.... we've seen entire automation suites go down after a single navigation update.
Curious how CoWork handles dynamic test data mid-execution. if a flow requires an OTP or an auth password during the run, can that be injected in real time or does everything need to be pre-configured before the session starts?
QApilot
@harini_mukesh There are a couple of we handle test data on CoWork, depending on the type of the test data. The user can choose to plug in the test data as part of the natural language test context that is given to CoWork. CoWork will make use of it as needed.
Otherwise, if CoWork comes across an input field like an OTP during its journey, it prompts the user to enter the input, and once the user does that, it continues to autonomously execute the rest of the steps. So, yes. Depending upon the test data and user preference, it can be injected in real-time or pre-configured.
QApilot
Observer
Hey builders 👋
I am one of the makers behind CoWork!
We built CoWork - an AI agent that drives real mobile apps step by step, planning each action, reading the screen, and adapting when things go off-script.
We kept hitting the same wall: mobile automation breaks the moment a layout shifts. So we wanted something that actually sees and reasons about the screen instead of leaning on brittle scripts.
We'd love your feedback and support. Drop your thoughts/questions in the comments below and one of us will reply!
QApilot
Hi everyone! Aakash from QApilot here.
I'm one of the makers behind CoWork, and I'm really excited to finally share what we've been building!
CoWork helps AI and humans work together to make test automation more reliable instead of chasing full automation. We'd really appreciate your support on Product Hunt today, and I'd love to hear what you think. Thanks for checking us out!
QApilot