See what passed and what's open before you ship
Sounds familiar? Bugs reach our customers before we find them, and every release breaks something else.
Developers test as they build, but they rarely have time to try every device, browser and odd path a customer might take. A QA (quality assurance) specialist uses your app, store or complex site the way customers do and logs each problem with the steps to reproduce it. Testing can be one round before a launch or continue on every release. How much there is to cover sets the effort, so the features and devices in scope are agreed on a short call before any quote. Before each release you can see what passed and what is still open.

What you get
- Test plan covering the features, devices and browsers in scope
- Written test cases for the core user journeys
- Test runs on real devices and browsers for each release in scope
- Bug reports with steps to reproduce, severity and screenshots
- Regression checks after each change, re-running tests on features that already worked
- Automated tests for critical flows, if agreed in the scope
- Release sign-off checklist listing open issues and their risk
Is this right for you?
- You are about to launch and want problems found before customers report them
- You have developers but nobody whose job is testing their work
- You see old bugs come back after each new release
- You want a second check on an app another team built
What it changes
Problems caught on the test version
The main customer journeys have been run on real devices, and what the testers found is logged and ranked before release.
Bug reports developers can act on
Each report carries steps, screenshots and a severity level. Developers can go straight to reproducing and fixing the problem.
A release decision with the facts in view
The sign-off checklist shows what passed, what is still open and how serious each open item is.
Scope and delivery
How we deliver it, what we need from you, what is not included. Timeline: Agreed after a short call; plan for 1–3 weeks for a pre-launch round, or ongoing alongside your releases
How we deliver it
-
Agree on what gets tested
The QA specialist reviews your app and specs, then writes a test plan naming the features, devices and browsers, and which issues would block a release.
-
Write and run test cases
Core journeys such as sign-up, payment and data entry are tested step by step. Unscripted exploratory testing then looks for what the written cases miss.
-
Log and retest bugs
Each issue goes into your tracker with steps to reproduce and a severity level. It is retested once your developers fix it.
-
Sign off each release
A short checklist shows what passed and what is open before the release goes out. When testing continues monthly, the regression checks run again on every release.
What we need from you
- Access to a test version of your app, store or site
- Test accounts and sample data for each user role
- Specs, designs or a feature list describing expected behavior
- Access to your bug tracker, such as Jira, Linear or GitHub Issues
What's not included
A specialist looks at your situation first, so the scope is agreed after a short call.
Not included
- Fixing the bugs found, unless that is part of a build or support scope (see App support & maintenance)
- Security penetration testing, which needs qualified partners and your written authorization
- Load testing at scale (ask about Load and performance testing)
Where it fits
What usually follows, what may already be in place, and what is planned alongside, with the reason for each.
This service: Testing & QA
3 connected services
Keeps it running
Keeps it working after launch.
-
App support & maintenance
After launch, updates are tested on a private copy of the app before release, and bugs are fixed within an agreed monthly capacity.
From build to ongoing support
-
Custom web applications
Apps & Custom Software
-
Testing & QA
Apps & Custom Software
This service
-
App support & maintenance
Care & Support
-
Ongoing development & improvement
Care & Support
Part of these packages
-
Digital product & MVP launch
Build and test: The first version, or the portal or tool, is built in stages, each ending with a review, and tested before each release.
Common questions
Can't our developers test their own work?
They should, and good developers write tests as they go. A separate tester comes to the app as a customer would, on the phones and browsers your customers actually have.
Do you need access to our code?
Only if automated tests are being added to your project, which is agreed in the scope. Other testing runs on a test version of the product, using test accounts for each user role and a description of how it should behave.
Is this a security test?
Functional testing includes basic checks, such as whether one user can see another user's records. A penetration test, where a specialist tries to break in on purpose, is done only by qualified partners with your written authorization and is scoped separately.
Can testing continue after launch?
Testing can run monthly alongside your releases, with what each month includes stated in writing. If you also need the bugs fixed, App support & maintenance covers fixes and regression checks on the live app.