We find it before your users do
Pre-release QA Checks
We run your sign-up, login, and checkout flows before you ship
If your users are finding the bugs for you, those bugs are already too late.
What it looks like on a team with no QA
You build the feature, click through it a few times yourself, and ship. There is no time to check how it looks in another browser, what overlaps on a narrow screen, or what happens when a field is left empty. So users find it first, and only some of them tell you.
What we do
-
E2E tests for the critical flows
Sign up, login, checkout, posting: the flows that must not break become automated tests that a real browser walks through.
-
Repeated across combinations
We run the same flow again across browsers and screen sizes. Anything that only breaks in one combination shows up here.
-
Cross browser checks
We check that the same flow behaves the same way in Chrome, Safari, and Firefox, and surface the places where browsers differ.
-
Mobile screen checks
We look for anything cut off, overlapping, or impossible to tap on a narrow screen, and send a screen recording with it.
-
Edge case exploration
Empty values, very long input, slow networks, double clicks, the back button: we deliberately push the conditions that break things in real use.
The bug report
Each item comes with reproduction steps, a screen recording, and a severity. It is written so you can go straight to fixing it without having to come back and ask us. If there is nothing to fix, we write that too.
How to start
-
Send the address and the critical flows
Tell us your service address and the flows that must not break. If you do not have that list, we will put it together with you.
-
Writing the tests
We turn the flows you sent into automated tests that a real browser walks through.
-
The full run and report
We attach the tests to the critical flows, run every combination, and write up what came out.
A good fit for
- Indie developers heading into launch with no QA
- Small teams that ship features fast and keep hitting the same regressions
- Services with flows like checkout or sign up where a break stops revenue
Frequently asked questions
- Do we have to hand over our code?
- No. We test through the browser from your public address, the way a user would. No repository access is needed.
- Can you test screens behind a login?
- Yes. Create one test-only account for us and we will cover the flows after login as well.
- Do you fix the bugs too?
- This check covers finding them and writing them up. If you want the fixes as well, those are quoted separately as per-job development.
- How far does the check go?
- We work from the critical flows such as sign-up, login, and checkout, and cover browsers, mobile screens, and edge cases.
Run it once before you launch
Send us your service address and the flows that must not break, and we will map out the scope of the check first.