Fewer bugs in production
We test the journeys that matter most to your users and your revenue.
Service 14 of 15
QA & software testing
Manual and automated testing that catches bugs before your users do.
- Typical timeline
- 2–8 weeks
- Pricing
- Fixed quote
- Team
- QA lead + test engineer
Our 3 promises
Your releases. Our goal.
Three promises we make on every testing project.
Faster releases
Automated tests in your pipeline, so releases stop waiting on manual checks.
Clear reports
Plain-language results with steps to reproduce every issue.
Tech stack
The stack behind your qa & software testing
Proven, well-supported tools at every layer. Picked for your product, never for our habits.
- AutomationCypress
- AutomationMost requestedPlaywright
- AutomationSelenium
- AutomationAppium
- Unit & APIJest
- Unit & APIMost requestedPostman
- Unit & APIPytest
- Unit & APIPact
- PerformanceMost requestedk6
- PerformanceJMeter
- PerformanceLighthouse
- Accessibilityaxe
- AccessibilityWCAG 2.2
- AccessibilityScreen readers
- DevicesBrowserStack
- DevicesReal iOS
- DevicesReal Android
- PipelinesGitHub Actions
- PipelinesGitLab CI
- PipelinesJira
What’s included
What you get
Everything in scope, from a test plan to automated checks on every release.
01StartTest strategy
A risk-based plan that focuses testing where it counts.
Read more +Show less −
Test strategy is a risk-based plan that puts testing effort where bugs would hurt your business most. You get a risk review, a test plan and a fixed quote for the testing work. It usually takes about a week.
What you get
- Risk review of your product's key features and user journeys
- Test plan covering what to test, how and when
- Split of manual testing and test automation
- List of devices, browsers and tools to use
- Fixed, itemised quote for the testing work
How it works
- We learn your product, users and past problem areas
- We rank features by business risk and change rate
- We draft the test plan and review it with you
- You approve the plan and the fixed quote
Good to know: Share your bug history and support tickets, as they show quickly where testing will pay off most.
02TestManual testing
Exploratory and regression testing on real devices.
Read more +Show less −
Manual testing is hands-on testing by a QA engineer who uses your product as real users would, on real iOS and Android devices and main browsers. You get exploratory testing that finds usability and edge-case problems, plus regression checks before each release. Every bug comes with clear steps to reproduce it.
What you get
- Exploratory test sessions on your key user journeys
- Regression testing before each release
- Testing on real iOS and Android devices and main browsers
- Bug reports in Jira with steps, screenshots and severity
- Retest of every fix before it is closed
How it works
- We write test cases for your key journeys
- We run exploratory and regression sessions each sprint
- We log and rank bugs by severity
- We retest fixes and confirm release readiness
Good to know: Give testers a stable test environment with realistic data, so results reflect what real users will see.
03BuildTest automation
End-to-end and API tests that run in your pipeline.
Read more +Show less −
Test automation is a set of end-to-end and API tests that run automatically every time your code changes. We write them in Playwright or Cypress, with Postman or Pact for APIs, and run them in GitHub Actions or GitLab CI. The tests live in your repository, so they keep protecting every release.
What you get
- End-to-end tests for your key user journeys in Playwright
- API tests for your main endpoints
- Tests running in your CI/CD pipeline on every change
- Clear pass and fail results on each pull request
- Guide for your developers to add and update tests
How it works
- We pick the journeys worth automating first
- We write tests and add them to your pipeline
- We fix flaky tests so results can be trusted
- We hand over and train your team
Good to know: Automate stable, high-value journeys first; automating features that still change every week wastes effort.
04TestPerformance & accessibility
Load, speed and WCAG checks before launch.
Read more +Show less −
Performance and accessibility testing checks that your product stays fast under load and that people with disabilities can use it. We run load tests with k6 or JMeter, speed checks with Lighthouse, and accessibility checks against WCAG 2.2 with axe and screen readers. You get a prioritised list of fixes before launch.
What you get
- Load test showing how many users your system handles
- Page speed results for key pages on mobile
- WCAG 2.2 accessibility audit using axe and manual checks
- Screen reader testing of key journeys
- Prioritised list of fixes with clear explanations
How it works
- We agree expected traffic and key pages to test
- We run load, speed and accessibility tests
- We report results and the fixes that matter most
- We retest after fixes are made
Good to know: Run load tests on an environment that matches live, otherwise the results will not reflect real traffic.
05LaunchReporting
Dashboards and reports your whole team can read.
Read more +Show less −
Reporting turns test results into dashboards and short reports your whole team can read, not only developers. You get clear bug reports, a view of test coverage and release notes for each release. Reports are shared at the end of every sprint and before each release.
What you get
- Bug reports ranked by severity and business impact
- Test coverage summary for key features
- Release readiness report before each release
- Release notes listing fixes and known issues
- Dashboard of test results in Jira or your CI tool
How it works
- We agree what each audience needs to see
- We set up dashboards from your test and bug data
- We share a report at the end of each sprint
- We sign off each release with a readiness report
Good to know: An independent bug report is useful at acceptance sign-off when another agency built the software.
How it works
From idea to launch
Every service runs through the same five steps. Here is what each one means for QA & software testing.
01of 05
UnderstandWeek 1Once
We learn your product, users and where bugs hurt the most.
You getTest brief
What we do
- Walk-through of your product
- Review past bugs and releases
- Agree the critical journeys
You get
- Test brief
- Risk list
- Critical journey map
From you
- 1–2 hours with your team
- Test accounts and environments
Tools
- Notion
- Jira
02of 05
PlanWeek 1–2Once
Test plan, tools and a fixed quote you approve.
You getFixed quote & test plan
What we do
- Risk-based test plan
- Automation scope and tools
- Device and browser list
You get
- Fixed, itemised quote
- Test plan
- Timeline with milestones
From you
- Review and approve the plan
Tools
- TestRail
- Jira
03of 05
TestEach sprint↻ Repeats
Manual testing and automated tests, sprint by sprint.
You getTested build every sprint
What we do
- Exploratory and regression testing
- Automated end-to-end and API tests
- Bugs logged with clear steps
You get
- Bug reports
- Automated test suite
- Coverage report
From you
- Fix the bugs found
- A contact for questions
Tools
- Playwright
- Postman
- BrowserStack
04of 05
ReleaseEach release↻ Repeats
Release checks, performance and accessibility tests.
You getRelease sign-off
What we do
- Regression run before release
- Load and accessibility checks
- Release report
You get
- Release report
- Performance results
- Accessibility results
From you
- Release approval
Tools
- k6
- axe
05of 05
Support & growOngoing↻ Repeats
Keeping tests up to date as your product grows.
You getOngoing improvements
What we do
- Maintain and extend tests
- Tests in your pipeline
- Monthly quality review
You get
- Monthly update
- Quality trends
From you
- Monthly 30-minute review
Tools
- GitHub Actions
- Jira
FAQ
QA & software testing questions
What types of testing do you offer?
Functional, regression, test automation (Playwright, Cypress, Appium), performance and load, accessibility (WCAG 2.2) and security checks, for web and mobile.
How long does a QA engagement take?
Most of our testing projects run 2–8 weeks. Ongoing QA can also run alongside your development sprints.
Can you test software another agency built?
Yes. We test independently and give you a clear, prioritised bug report, which is useful before launch or acceptance sign-off.
Manual or automated testing: which do we need?
Usually both. Automation covers repeated regression checks cheaply; manual testing finds usability and edge-case issues that scripts miss.
Do we keep the automated tests?
Yes. Test suites live in your repository and run in your CI pipeline, so they keep protecting every release.
Who owns the code?
You do. All IP is assigned to you in the contract, and the code, accounts and documentation are yours from the first sprint.
Let’s talk
Let’s talk
A 30-minute call with an engineer and a clear next step for your project.