QA testing and automation
QA means checking the software works before users find out it doesn’t, and automation repeats those checks on every change, so last month’s work gets checked again each time. We’ll test software another team built, too. Launch starts from $1,000 for a QA and automation audit.
The problem
Your users shouldn’t be the ones who find the bug.
But when nobody tests on purpose, that’s exactly who does: the customer whose payment form froze, the one whose phone shows only half of the page. It compounds. A fix can break something else, because nothing checks the old parts when the new part ships.
What you get
- A written test plan in plain words: what we check, on which screens and devices
- Manual checks on the flows your users depend on, like sign-up, payment and the forms
- Automated checks that run on every change, so an old feature can’t break quietly
- Layout checks from a 320 px phone screen up
- Keyboard and screen-reader checks, so people who don’t use a mouse can still get through
- Tests on the Android build as well as in browsers, when your product has an app
- A report you can read: what failed, where, and how to see it yourself
How it runs
The brief.
What the software does, and which flows can’t break.
Plan and price.
You’ll see the test plan and the price before we run a single check.
Milestones.
Each one ends with a link to the results. Every failure links to the screen that failed, with the steps to see it yourself.
Handover.
The tests, the test plan and the accounts they run under move into your name.
On the software we build, testing happens inside every milestone, not as a phase at the end.
Proof
Our own windowsweep runs its checks on every change, in a public repository. Open the check history.(opens in a new tab) (opens in a new tab) It shows what ran, when, and whether it passed. The same checks run on the software we build for you.
What it costs
The QA and automation audit falls under Launch, from $1,000, while on software we build, testing is inside the price, so there’s no separate QA line on your estimate. After an audit, fixing what it found gets its own estimate, if you want us to do it.
Questions
Checking the software works before users find out it doesn’t, repeated on every change.
Yes. That’s what the QA and automation audit in Launch is for. Send the brief with access to a test build.
The flows that cost you money when they break: sign-up, sign-in and payment. Then the forms your users fill in most.
No. On software we build, testing happens inside every milestone and is part of the price in your estimate.
Start
Name the one flow that would hurt most if it broke. We’ll test that one first.
Page updated .