We try to break it before your users do.
AI writes tests that pass. We write tests that catch things.
A build you're nervous about shipping. Maybe some tests. Maybe none.
A test suite that runs in CI, a bug list with reproduction steps, and confidence about what you are shipping.
What's actually included.
Manual exploratory testing, done by someone trying to break it on purpose.
Automated unit and integration tests around the logic that matters.
End-to-end tests for the flows that make you money.
Cross-browser and real-device testing, including the old Android nobody checks.
A regression suite wired into CI so the same bug cannot come back twice.
What we work with.
The suite runs in the CI you already have. We are not going to ask you to move to a different one so our tests feel at home.
Fair things to ask.
We have tests already.
Good. We'll tell you which ones are load-bearing and which just assert that true is true. AI-written suites are usually full of the second kind.
How long does it take?
A first pass on a typical app is a few days. Full coverage depends on how big the product is and how much of it is worth covering.
Do you test on real devices?
Yes, for anything mobile-facing. Emulators miss too much.
What kinds of tests do you write?
Enough unit tests to pin the logic, integration tests where systems meet, and end-to-end tests for the flows that make you money.
Will the suite run in our CI?
Yes. That's the point. A suite nobody runs is documentation.
What if the tests end up slow?
We'd rather leave you a fast suite people actually run than a thorough one they learn to skip.
Do you do manual testing too?
Yes, and it finds the strangest bugs. Automation checks what you thought of; a person finds what you didn't.
Will you fix the bugs you find?
We can. Finding and fixing are separate pieces of work, so it's your call.
Can you test something we can't give you the source for?
Yes, black-box. Expect it to be slower and less thorough, because we're guessing at the inside.
What do we have at the end?
A suite in your repo, a bug list with reproduction steps, and a note on what we chose not to cover and why.