Release day = click-through day
Someone spends hours clicking through the app before every release. It is boring, easy to rush, and it holds up deploys.
We write the end-to-end tests your team never gets round to. They open a real browser and click through your real product, and they run in your CI, so a broken sign-up, checkout or dashboard gets caught before a customer sees it.
Someone spends hours clicking through the app before every release. It is boring, easy to rush, and it holds up deploys.
A small change in one place breaks sign-up or checkout somewhere else, and customers find it before you do.
Your devs are shipping features. Nobody has the time or the specialist knowledge to set up a proper E2E suite.
You don’t get a PDF or a dashboard subscription. You get real code in your repo that runs every time someone opens a pull request.
Broken code can’t merge until the tests pass. The check runs across browsers and a phone-sized screen.
Plain TypeScript. No platform, no licence fees.
Before handover, the whole suite runs 20 times in a row. It must pass all 20.
Every failure comes with a video, a screenshot and a step-by-step trace, so your devs see exactly what broke and where.
Failures on your main branch are posted to Slack or Teams, with a link to the report.
A clear README, a recorded walkthrough and a live session, so your devs can add tests themselves.
This is a pretend online shop. Pick a change a developer might make and watch what happens. Harmless changes go straight through. Changes that would hurt your customers get stopped before anyone sees them.
Pick a change a developer might make
Some are harmless and some would hurt your customers. Can you tell which will get through?
2 × Pro seat · R250 each
30 minutes. We map your product and pick the flows where a bug would hurt most.
A written scope listing every flow, the price in rand and a delivery date. The NDA is signed before we see any code.
You give us repo access, a QA environment, locked test accounts and a short screen recording of each flow.
We write the tests in a branch of your repo, using AI to draft them and an engineer to review, run and stabilise every one. Every Friday you get a short demo of new tests passing.
The tests run on every pull request, and failures come with video, traces and screenshots.
A merged PR, a README and a live walkthrough, so your team can run, read and extend the suite.
| Criteria | Greenlight | Hire in-house | DIY with AI tools | Keep testing manually |
|---|---|---|---|---|
| Cost to get a working suite | From R18 500 once-off | ≈ R40k–R70k / month salary + recruitment | Your devs’ time, then more of it fixing what breaks | Hours of staff time every release |
| Time to first tests in CI | 2–3 weeks | 2–3 months (hire + ramp-up) | Days to generate, weeks to make reliable | Never automated |
| Proven stable before you rely on it | Yes, 20 green runs in a row | Depends on the hire | Rarely. Passing once isn’t the same as passing every time | N/A |
| Runs on every pull request | Yes | Eventually | If someone wires it up | No |
| You own the code | Yes, it lives in your repo | Yes | Yes | N/A |
| Long-term commitment | None. Optional monthly plan | Permanent headcount | None | None |
In-house figure is a rough 2026 range for a mid-level QA automation engineer in SA, before benefits.
Works with your stack
No hourly surprises. Pick a package, add a monthly plan if you want the suite kept green.
Your few make-or-break journeys, checked on every deploy.
The suite most product teams actually need.
Release-gate coverage for larger or regulated platforms.
End-to-end (E2E) testing checks a whole journey through your product the way a customer would do it: open the site, sign up, log in, pay, get the confirmation email. An automated E2E test does this in a real browser on every change, so if any step breaks, the change is blocked before it reaches your users.
We wrote a plain-English guide to end-to-end testing that explains how it differs from unit and manual testing.
By default, Playwright with TypeScript. It is fast, free, and runs Chromium, Firefox and Safari (WebKit). If you already have a Cypress or Playwright suite, we can extend and stabilise it instead of starting over.
Yes, we use AI to draft tests faster, which is part of why we can get tests into your CI in weeks. But every test is read, run and stabilised by an engineer before it reaches your repo.
AI is good at writing a test that passes once. It isn’t good at deciding which flows matter most, setting up clean test data through your API, keeping tests independent of each other, or proving they pass 20 times in a row. That judgement is what you’re paying us for, and it’s the difference between a suite your team trusts and one they learn to ignore.
Yes. Chatbots, AI search and generated content give slightly different answers every time, so we don’t check for exact wording. Instead we test the journey around them: the feature loads, responds within a sensible time, handles errors and empty answers, and returns something in the right shape. Ask about it on the call.
You do. Everything is committed to your own repository. There are no licences, no platform fees and no lock-in. If we never speak again, the suite keeps running.
Tests find elements by accessible roles and data-testid attributes, not by fragile CSS paths, so colour, layout and copy tweaks don’t break them.
When a flow changes for real, the README shows your devs how to update the test. Or a Keep Green plan means we handle it.
We design against flakiness from the start: no fixed waits, test data set up through your API, and each test isolated from the others. Before handover, the whole suite runs 20 times in a row in CI and has to pass every time. Every package also includes a fix warranty.
No, never. We work only against a QA or staging environment, using dedicated test accounts. See exactly what we need.
We sign an NDA before we see your code. We only ask for the access we need, we never use real customer data, credentials are kept in your CI secrets and a password manager, and all our access is removed at handover. Your code is never pasted into public AI chatbots. We only use AI tools on business terms that don’t train on your code, and if you’d rather we use none at all on your project, just say so.
Mobile web and responsive layouts are included from Core Coverage upwards. Native iOS and Android apps (with Maestro or Appium) are quoted separately. Ask on the call.
50% deposit to book your start date and 50% on handover, by EFT. Monthly plans are billed in advance and you can cancel with 30 days’ notice. International clients can pay in USD, EUR or GBP.
A free 30-minute call. We pick your riskiest flows together and you get a fixed quote within 48 hours. No obligation.