Testing and QA

Manual and automated testing across real devices, so every release is checked against the situations people actually run into.

Discuss your project

How the work is done

Testing is planned alongside features, not after them. Each release gets a test plan covering new work, regression risks and device behaviour such as permission changes, low storage, weak connectivity and interrupted camera sessions.

Repetitive checks are automated with Espresso, XCTest and Maestro and run in continuous integration on every merge. Exploratory testing on physical devices covers what automation misses, and every defect is logged with steps, device, OS version and a screen recording.

What’s included

  • Test strategy and release test plans
  • A device matrix based on your audience
  • Automated UI tests with Espresso, XCTest and Maestro
  • Review of unit and integration test coverage
  • Exploratory and accessibility testing
  • Pre-submission checks against store policies
  • Performance and battery profiling

What you receive

  • Test plans and results for each release
  • Defect reports with reproduction steps
  • Automated test suites in your repository
  • A release readiness summary

How we measure quality

These are the measures we track and report on. Target values are agreed for each project rather than promised in advance.

  • Defects found before release compared with after
  • Automated test pass rate
  • Crash-free sessions after release
  • Time from defect report to fix
Abstract composition of coloured code-line shapes on a cobalt background for the Testing and QA service

Platforms and formats

  • Physical Android and iOS devices
  • Emulators and simulators
  • Cloud device farms such as Firebase Test Lab

Related work

Common questions

Can you test an app built by another team?

Yes. We start with a baseline test pass and a written report, which gives the development team a prioritised list to work through.

How many devices do you test on?

The matrix is set from your audience data and the features involved. Camera and file features need more real hardware than a simple content app.

Discuss your project

Timelines and pricing are quoted per project after a discovery call. Fields marked * are required.

Prefer email? Write to [email protected]. Send any documents to the same address.