QA testing.
Websites and apps tested on real phones, browsers and slow connections. For our own builds, or on its own for a site or app someone else built.
What’s included
(06)Your site or app looks fine on the laptop it was built on, and you want to know what breaks before your customers find out.
-
Devices and browsers
Tested by hand on real phones, tablets and desktop browsers, including the older and cheaper ones your customers use.
-
Forms, journeys and payments
Sign-up, enquiry, cart and checkout run end to end, with wrong inputs, back buttons and interrupted sessions included.
-
App testing
Mobile apps checked for crashes, interruptions, permissions, different OS versions and patchy networks.
-
Speed and accessibility
Load times measured on slow connections, and pages checked with keyboards, screen readers, zoom and contrast against WCAG.
-
Automated checks
Repeatable checks for the things that tend to break again after each change, so people can spend their time on judgement.
-
Bug reports
Every issue written up with where it happened, on what device, how to see it again and how serious it is.
When you need it
- You are about to launch and nobody has tested it outside the team.
- Customers are reporting bugs you cannot reproduce.
- Your agency or developers built it, and you want an independent check.
- Every new release seems to break something old.
- You are not sure the site works for people using screen readers or keyboards.
How it runs
(04)You get a written scope, a fixed price and a start date before anyone begins.
-
Scope
Which pages, journeys, devices and browsers get tested, agreed in writing, based on who your customers are.
-
Test
Manual testing on real devices, plus automated checks where repeating them is worth it.
-
Report
A written report of what broke, where, on what, and how to see it again, ranked by how much it matters.
-
Retest
Once fixes are in, we test the same issues again and confirm what is closed and what is still open.
What you leave with
- A test plan: what is tested, and on what
- Written bug reports, ranked by severity
- Speed and accessibility findings
- Automated checks for repeat problems
- A retest report after fixes
Start your project with us
FAQ
Answered questions.
Yes. QA is available on its own. We do not need to have built it, only access to a test version and a list of what it is meant to do. You get a written report your developers can act on.
Automated checks repeat the same steps quickly and catch things that break again after a change. Manual testing is a person using the product and noticing what feels wrong. We use both, each where it earns its place.
Yes. Apps are checked on real devices across OS versions and networks, for crashes, interruptions, permissions and the things store review looks at.
Where it happened, on which device and browser, the steps to see it again, what was expected and what happened instead, with a screenshot or recording. Read more in Test it before your customers do.
