Skip to content
NDABefore code accessIPAssigned to youTermsMonth to monthExitNo penalty
Talk To An Engineer
QA And Testing

Testing That Finds Problems Before Your Users Do

We test web and mobile products by hand and with automated tests, and report what we find in a form your developers can act on.

  • Test plan agreed before testing starts
  • Defects reported with steps to reproduce
  • Automated tests are yours to keep
Discuss Your ProjectSee How We Build

What QA And Testing Covers

Manual testing is a person using the product the way a customer would, including the ways a customer should not. Automated testing is code that repeats checks on every change, so a fix in one place does not break another.

Most products need both. We agree with you which journeys matter most, test those first and automate the checks that are repeated on every release.

What We Test

  • Manual Testing

    Structured and exploratory testing of the journeys that matter most.

  • Regression Automation

    Automated checks that run on every change and catch what has broken.

  • API Testing

    Checks on the services behind the screens, including error handling.

  • Performance Testing

    How the product behaves under load, measured before launch.

  • Device And Browser Testing

    Testing across screen sizes, browsers and operating system versions.

  • Accessibility Checks

    Keyboard use, contrast and screen reader behaviour on key screens.

Who This Is For

  • Teams Close To Launch

    You need an independent check before the product reaches customers.

  • Development Teams

    Your developers test their own work and defects still reach production.

  • Product Owners

    Each release breaks something that used to work, and you want that to stop.

How Testing Runs

  1. 1
    Step 1

    Plan

    We agree what is in scope and which journeys matter most.

  2. 2
    Step 2

    Write Test Cases

    Test cases written so anyone can repeat them.

  3. 3
    Step 3

    Test

    Testing carried out and defects reported as they are found.

  4. 4
    Step 4

    Automate

    Repeated checks turned into automated tests.

  5. 5
    Step 5

    Report

    A written summary of what was tested, what failed and what remains.

The full process, from first call to support after launch, is on the How We Build page.

What You Receive

  • Test Plan

    Scope, approach and the test cases used.

  • Defect Reports

    Each with steps to reproduce, expected and actual result.

  • Automated Tests

    In your repository, ready to run on every change.

  • Summary Report

    What was covered and what we recommend before release.

Ways To Work With Us

Pick the model that suits how clear the scope is. We quote in writing before you commit.

Tell Us What You Want To Build

Helpful to include

  • What the product should do
  • Who will use it
  • Anything already built
  • Your target date

What happens next

  • We read your brief and reply within two working days
  • A scoping call to agree goals and must-haves
  • A written proposal: scope, timeline and cost

QA And Testing Enquiry

No obligation. We sign an NDA before you share anything confidential.

QA And Testing Questions

Have More Questions?

Yes. Independent testing is often more useful, because we come to the product without assumptions about how it should be used.

Manual testing is enough for a one-off check before launch. If you release regularly, automating the repeated checks saves time on every release and catches regressions early.

In your own tracking tool, or in a shared report if you do not have one. Each defect has steps to reproduce, the expected result, the actual result and a severity.

Yes. Testers can work alongside your developers sprint by sprint, or test a release as a separate engagement.

Have Something To Build?

Tell us the idea and the timeline. We will reply with questions, then a written proposal.

Talk To An EngineerAll Services