Skip to content

Service · Quality

QA Testing

Commission independent QA when you need someone other than the builders to tell you whether a release is safe. We rank what could go wrong by business impact, test it by hand and by machine across the devices your users carry, and give your release owner clear evidence to decide on.

Coverage ranked by business risk

Automated regression your pipeline can run

Defects reported with steps, evidence and severity

Deliverables

What a QA testing engagement delivers.

01Delivered

A risk-ranked test plan

Critical journeys, user roles, integrations and data conditions ranked by the cost of failure, so the most testing goes where a defect would hurt revenue, safety or trust most.

02Delivered

Exploratory test sessions

Time-boxed sessions led by charters, probing edge cases, interrupted flows, odd inputs and role permissions that scripted cases tend to miss, each written up with what was covered.

03Delivered

Automated regression suite

End-to-end tests in Playwright for web and Appium, Detox or Maestro for mobile, plus API tests at the service layer, wired into your CI so they run on every merge.

04Delivered

Device and browser coverage

A matrix chosen from your analytics, run on physical phones and cloud device farms, covering the OS versions, screen sizes and browsers your users actually have.

05Delivered

Release readiness report

For each release, a summary of what was tested, open defects by severity, known risks accepted and a clear recommendation for your release owner.

Early decisions

Technical decisions we settle early in QA testing.

01Decided

What counts as critical

Sign-up, payment, data entry that cannot be redone and anything regulated usually top the list. We agree the ranking with your product and engineering leads before writing a single test case.

02Decided

Which layer each check belongs in

Many checks are cheaper and steadier as API or component tests than as full browser runs. We push tests down to the lowest layer that still catches the defect, keeping the end-to-end suite small.

03Decided

Test data and environments

Realistic accounts, edge-case records and a stable staging environment matter as much as test scripts. We define seed data and reset routines so results do not depend on yesterday’s leftovers.

04Decided

Severity and blocking rules

Agreeing what makes a defect critical, major or minor, and which severities block a release, prevents arguments on release day and makes reports comparable over time.

05Decided

Handling flaky tests

A suite that fails at random is soon ignored. We quarantine unstable tests, find the cause, usually timing or shared data, and fix it rather than adding retries that hide real failures.

06Decided

Non-functional checks in scope

Load, accessibility and basic security checks can be part of the engagement or left to specialists. We decide which, so nobody assumes coverage that was never planned.

Engagement

How a QA testing engagement runs.

  1. 01Phase 1

    Learn the product and its risks

    We walk through the product with your team, read requirements and past incident reports, review existing tests, and turn all of it into the risk-ranked plan.

  2. 02Phase 2

    Explore and stabilise

    Exploratory sessions on the riskiest areas find the defects that matter now, while we set up environments, test data and the device matrix for repeatable work.

  3. 03Phase 3

    Automate the regression core

    The journeys that must never break are automated first and connected to CI, with results published where your developers already look.

  4. 04Phase 4

    Release cycles and handover

    We test each release against the plan and report readiness. At the end your team receives the suite, the plan, the data scripts and guidance on extending them.

Fit

When independent QA is the right choice.

01Good fit

Defects keep reaching users

If customers find bugs before your team does, an outside view of where coverage is thin, and a regression suite to close it, usually pays back quickly.

02Good fit

A high-stakes release is coming

A payment change, a migration, a public launch or a regulated feature deserves evidence from someone with no stake in having built it.

03Good fit

Developers test their own work only

Teams without a dedicated tester often check that features work as intended, but not how they fail. Independent QA adds the second perspective.

Testing is about risk, not counts

A large number of test cases says little about quality. What matters is whether testing covers the things that would cost you most if they broke. A typo on a settings screen and a double charge at checkout are both defects, but they deserve very different amounts of attention.

We begin by ranking journeys, roles and data conditions by the damage a failure would do, and that ranking shapes everything after it: where exploratory time goes, which tests are automated first and what blocks a release.

Why people still test by hand

Automation is excellent at confirming that known behaviour has not changed. It is poor at noticing that a flow is confusing, that a message makes no sense or that an unusual sequence of actions corrupts data. Skilled exploratory testing finds those problems. We run it in focused sessions with written charters, so it is accountable rather than ad hoc.

Automation that stays trusted

An automated suite earns its keep only if developers trust its results. Slow, flaky end-to-end suites get ignored. We keep the browser and device layer small and focused on critical journeys, push other checks into faster API and component tests, and treat any flaky test as a defect in its own right.

Testing on the devices people own

Users run older phones, manufacturer-modified Android builds, small screens and large text settings. Emulators help, but they miss camera behaviour, push delivery, memory pressure and how a real keyboard covers a form. We set the device matrix from your analytics and test on physical hardware for the journeys that depend on it.

Evidence for the release decision

QA does not own the decision to ship; your release owner does. Our job is to give them clear evidence: what was tested, what was found, what remains open and what risk that leaves. A short, honest readiness report lets them ship with confidence or delay with good reason, rather than relying on how the team feels on the day.

FAQ

Questions to resolve before the build.

01What drives the cost of QA testing?

The number of critical journeys and roles, platforms and devices in the matrix, how much automation is wanted, the state of test environments and data, release frequency, and whether load, accessibility or security checks are included.

02How long does a QA engagement last?

Some engagements cover one release; others run alongside development for a period. Duration depends on the product’s size, how often you release, how much automation is built and how stable your environments are. We agree the scope and end point at the start.

03What do we keep when the engagement ends?

The test plan, exploratory session notes, the automated suite in your repository and pipeline, test data scripts, the device matrix, all defect reports in your tracker and the readiness reports for each release tested.

04Who owns the tests and reports?

You do. Test code is committed to your repositories under your licence, defects live in your tracker, and reports are yours to share with auditors or partners. Paid device farm accounts are set up in your name or billed through, as you prefer.

05How is our QA work accepted?

Against the plan agreed at the start: the listed journeys covered, the agreed automated tests running green and stable in your pipeline, and readiness reports delivered for each release in scope.

06What does QA testing not cover?

Fixing the defects found, unless that is added to the scope, writing product requirements, and full security penetration testing. Testing also cannot prove a product has no bugs; it reduces risk in the areas the plan covers.

Primary sources

References behind this page

Dated official documentation, standards, and research that support the factual claims on this page.

  1. 01
    Playwright documentation

    The browser automation framework used for end-to-end web tests.

  2. 02
    Appium documentation

    The open-source framework for automating native and hybrid mobile apps.

How to read this page

Scope, cost and timeline figures are planning guidance until confirmed in a written proposal. Diagrams and screens are illustrations, not client deliverables, and source-code rights and handover follow the signed agreement. See the delivery process and the full disclaimer.

Next decision

Turn the brief into an accepted product scope.

Define outcomes, constraints, evidence, rights and handover before delivery begins.

Commercial rights, repositories, environments, documentation, acceptance and handover remain contract-defined.