Mobile app testing: strategy, tools and best practices

How to test mobile apps effectively, from automated unit and UI tests to device coverage, beta testing, accessibility, performance and release checks.

By the UK Technology Hub teamPublished 4 minute read

The short answer

Effective app testing combines automated tests for logic and key user flows, testing across a representative range of real devices and operating system versions, beta testing with real users, and checks for accessibility, performance, security and poor network conditions. Automate what runs on every change, test manually what needs judgement, and use crash reporting to catch what slips through.

Mobile apps run on thousands of device and operating system combinations, on unreliable networks, with interruptions from calls and notifications. Bugs that reach users show up as crashes, bad reviews and uninstalls. A clear testing strategy catches problems before release.

The testing pyramid

Unit tests check individual functions and components. They're fast and should be the largest group.

Integration tests check how pieces work together, such as the app talking to an API.

UI or end-to-end tests automate real user journeys through the interface. They're slower and more fragile, so focus them on critical flows like sign-up, login, checkout and booking.

Manual testing covers exploratory testing, usability and anything hard to automate.

Our guide to automated testing explains these layers in more depth.

Tools

  • iOS: XCTest and XCUITest for unit and UI tests.
  • Android: JUnit for unit tests and Espresso for UI tests.
  • Cross-platform: tools such as Appium, Detox for React Native, and Flutter's integration testing.
  • Device clouds: services that run tests on many real devices remotely.

Device and OS coverage

You can't test everything. Choose a matrix based on your users' analytics:

  • The most popular devices and screen sizes.
  • The oldest OS version you support.
  • Mid-range and budget Android devices, not just flagships.
  • Tablets if you support them.

Emulators and simulators are great for fast development testing, but real devices reveal performance, camera, sensor and battery issues.

Real-world conditions

Test:

  • Slow, unstable and no network connections.
  • Interruptions: calls, notifications, switching apps.
  • Low battery and power-saving modes.
  • Device rotation and split screen.
  • Permissions denied or revoked.
  • Different languages and regions.
  • Updating from previous app versions with existing data.

Accessibility testing

Check flows with VoiceOver and TalkBack, large text sizes and contrast settings. Our guide to mobile app accessibility covers what to check.

Performance testing

Measure start-up time, scrolling smoothness, memory and battery on representative devices. Add performance checks to automated tests where possible.

Security testing

Review data storage, network traffic and API security, following recognised standards. Our mobile app security checklist covers the essentials.

Beta testing

Before public release, test with real users:

  • TestFlight for iOS lets you invite internal and external testers.
  • Google Play testing tracks support internal, closed and open testing.

Collect feedback and crash reports, and fix issues before wider release.

Continuous integration

Run automated tests on every code change through a CI pipeline, building the app and running unit and key UI tests automatically. This catches regressions early. See our guide to CI/CD for small teams.

Release checks

  • Version numbers and release notes updated.
  • Store listings and screenshots current.
  • Privacy disclosures accurate.
  • Analytics and crash reporting working.
  • Feature flags set correctly.
  • Staged rollout planned.

Staged rollouts

Release to a small percentage of users first, monitor crashes and reviews, then expand. Both stores support phased or staged releases.

After release

Crash reporting and performance monitoring tools show problems real users hit. Prioritise fixes by impact, and add tests for every bug fixed so it doesn't return.

Testing app updates and migrations

Some of the worst bugs appear when existing users update. Test upgrades from previous versions with real saved data, logged-in sessions and old settings, not just fresh installs. Check database migrations, cached data and stored preferences carefully.

Who should test

Developers test their own code, but fresh eyes find different problems. Involve product owners, support staff and real users in beta testing, and give them simple ways to report issues with screenshots and device details.

Testing checklists

Keep a short manual test checklist for each release covering sign-in, key journeys, payments, notifications and settings. Combined with automated tests, it gives confidence without slowing releases.

Keep tests maintainable

Tests need maintenance too. Remove obsolete tests, fix flaky ones quickly and refactor test code alongside app code. A smaller, reliable test suite is worth more than a large one nobody trusts.

How we help

Our mobile app development team builds automated test suites and device testing into every project. Our app development service runs beta programmes and staged rollouts, and our web app team tests the APIs your app depends on.

Frequently asked questions

Should I test on real devices or emulators?

Both. Emulators are fast for development; real devices reveal performance, hardware and network issues.

How many devices should I test on?

Choose a representative set based on your users' analytics, covering popular models, older OS versions and lower-end devices.

What should automated UI tests cover?

Focus on critical journeys such as sign-up, login, purchase and core features, rather than every screen.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

Mobile app security: a practical checklist

The most important security practices for mobile apps, based on industry guidance, covering data storage, authentication, network security, APIs and testing.

All web & mobile apps guides