Start a test run
[ Index 00 ] Independent software QA Web · Mobile · API · Accessibility London, UK

We break it so your users never will.

Apex Testers is an independent quality assurance studio. We embed with product teams to plan, run and automate testing — and hand back defect reports your engineers can reproduce in one read.

Book a scoping call See a real bug report

Press Q to see this page the way we see yours.

apex-runner checkout.spec.ts chromium · webkit · android
0 passed 0 caught 0 skipped 0.00s
DEF-TOTAL 0 defects logged across client projects
REPRO-1ST 0 reproduced by client engineers on the first attempt
T-FIRST-BUG <0h median from build drop to first report
CONFIGS 0 device, browser & OS combinations covered
01 Services

Seven ways to find out
what's broken.

AT-01 → AT-07
AT-01 Functional & regression Structured cases against your requirements, then a regression pack re-run every release so old bugs stay dead.
Deliverables
Test plan · traceability matrix · regression packs · release sign-off report
Typical engagement
2–6 weeks, then per-release
Works with
Jira, Linear, Azure DevOps, TestRail, Xray, Qase
AT-02 Test automation Playwright, Cypress, Appium and API suites wired into your CI — written so your team can maintain them without us.
Deliverables
Framework setup · CI pipelines · flake-rate monitoring · handover docs
Typical engagement
4–12 weeks
Works with
GitHub Actions, GitLab CI, CircleCI, Azure Pipelines, BrowserStack
AT-03 Performance & load k6 and JMeter scenarios modelled on your real traffic. We find the request that falls over at 2,000 users before launch day does.
Deliverables
Load model · soak, spike & stress runs · bottleneck report with traces
Typical engagement
1–3 weeks
Works with
k6, JMeter, Grafana, Datadog, New Relic
AT-04 Accessibility audits WCAG 2.2 AA with real assistive tech — NVDA, JAWS, VoiceOver, TalkBack — plus keyboard-only and 400% zoom passes.
Deliverables
Findings mapped to success criteria · code-level fixes · retest & statement support
Typical engagement
1–4 weeks
Standards
WCAG 2.2, EN 301 549, PSBAR 2018
AT-05 Mobile & device testing Real hardware, not just emulators. iOS and Android across OS versions, screen sizes, locales and bad networks.
Deliverables
Device matrix · install/upgrade paths · interruption & offline testing
Typical engagement
Per release or retained
Distribution
TestFlight, Firebase App Distribution, Play internal tracks
AT-06 API & integration Contract, schema and negative testing for REST and GraphQL. Auth, rate limits, idempotency — the things that break at 3am.
Deliverables
Contract tests · negative & boundary suites · third-party failure simulations
Typical engagement
2–6 weeks
Works with
Postman, Pact, REST Assured, Schemathesis
AT-07 Exploratory & UAT Senior testers with a charter and a timebox, hunting the bugs scripts don't think of. Plus facilitated UAT with your stakeholders.
Deliverables
Session charters · session notes · UAT scripts & sign-off log
Typical engagement
From 3 days
Best for
Pre-launch, redesigns, high-risk releases
02 Method

Five passes.
No guesswork.

T+0 → ∞
  1. T+0–2d 01

    Recon

    We read the product, the backlog and the incident history — then use it like your most impatient customer.

    → Risk map
  2. T+2–5d 02

    Plan

    Coverage set by risk, not by page count. What would hurt most if it broke gets tested first and hardest.

    → Strategy & case library
  3. T+5d → 03

    Execute

    Manual, automated and exploratory runs against every build you drop. Defects go straight into your tracker.

    → Defect reports
  4. Every sprint 04

    Report

    A plain-language quality status: what's safe to ship, what isn't, and what it costs to wait.

    → Release readiness
  5. Ongoing 05

    Regress

    Every fixed bug becomes a test. Every release re-runs them. Quality compounds instead of resetting.

    → Living regression suite
03 Evidence

Numbers we'd
rather show than say.

n = 41,870
FIG. 1

Production incidents per release

Average across retained clients, by months since onboarding.

−86% 8.6 → 1.2 incidents / release
month 0 → month 12
View as table
MonthIncidents / release
FIG. 2

Where the defects were

Share of all logged defects by category.

    Severity mix: 4% critical · 19% high · 46% medium · 31% low

    FIG. 3 — Specimen

    This is what lands
    in your tracker.

    Every report follows the same anatomy: one defect, one title, steps a stranger could follow, and evidence attached. If your engineer has to message us to understand it, we wrote it wrong.

    • ✓ Reproducible from the text alone
    • ✓ Exact build, device & data
    • ✓ Expected vs actual, with numbers
    • ✓ A regression test, already written
    BUG-2291 Severity: High P1 Open

    Checkout total drops discount code after switching delivery method

    Build
    4.12.0 (1187)
    Device
    iPhone 13 mini · iOS 17.5
    Browser
    Safari
    Repro
    10 / 10
    Steps to reproduce
    1. Add any two items to basket (subtotal £64.00).
    2. Apply code SPRING20 — total updates to £51.20.
    3. Change delivery from Standard (free) to Express (£4.95).
    Expected

    Discount persists. Total £56.15.

    Actual

    Discount silently removed. Total £68.95 — code still shown as “applied”.

    Notes

    Also on Android 14 / Chrome. Not on desktop. PATCH /api/basket/delivery response omits promo — likely recalculated without promo context.

    ▶ screen-recording.mp4 · 0:14 ⬚ basket.har ⬚ console.txt + AT-REG-0882 added
    04 Lab

    Real devices.
    Real bad Wi-Fi.

    0 / 0 busy
    Network profiles Fast 4GSlow 3GHotel Wi-Fi · 2% lossUnderground · offline ↔ onlineThrottled CPU ×4
    — The network

    1,200 testers.
    Everyday devices.

    UK · 18+
    0 testers in the Apex network across the UK

    Alongside our own testers, we run short paid sessions with a UK network of everyday users on their own phones, tablets and laptops — the devices and habits your customers actually have.

    • Sessions5–10 min
    • Reward$1–5 per test
    • WhoUK residents, 18+
    • ExperienceNone needed
    Join the network
    — House rules

    What we won't
    compromise on.

    4 / 4 enforced
    1. R.1

      A bug report is a product. If it needs a follow-up call, it failed.

    2. R.2

      Risk sets the coverage. We test what would hurt most, first.

    3. R.3

      Automation is a tool, not a trophy. We automate what pays back and explore the rest by hand.

    4. R.4

      We tell you when to ship. Not just what's broken — whether it matters.

    05 — Contact

    Start a
    test run.

    Tell us what you're shipping and when. We reply within one working day with a scoping call slot and a first look at the risks.

    Registered office Apex Testers Ltd 15d Hyde Park Mansions
    Cabbell Street
    London NW1 5AX
    United Kingdom Open in Maps ↗
    Hours
    Mon–Fri · 08:30–18:30 UK
    Response
    < 1 working day
    NEW TICKET AT-REQ-······
    04 · What needs testing?
    05 · Release window

    We use these details only to reply to your enquiry. See our Privacy Policy.