Can we use analytics cookies? They count visits and form use. We run no ads.

Test with AI

Mobile app test automation services for iOS and Android

Our mobile test automation services build and run automated tests for your iOS and Android app, native, hybrid or mobile web, on the devices and OS versions agreed with you. Tests are written in Appium or your existing framework, run in your CI and stay in your repository. We start with a one-week audit that ranks your app's flows by risk and fixes the device matrix before any test is written.

4.9 out of 5 on Clutch, from 7 client reviews

mobile-test-automation / mobile-audit.md

Flows ranked for the first pilot

Mobile audit
Login on iOS and AndroidOne scenario, platform-specific locators only where needed Automate
Purchase flow inside a web viewTest switches into the web view and back Automate
Push notification permission dialogDepends on OS version and device settings Device
First-run feel and gesturesA person judges it better than a script Manual

Zapple.Tech in figures

  • CodeceptJSFounded by the founders of CodeceptJS and Codeception, open-source testing frameworks
  • 32Test automation engineers and experts
  • 42Completed test automation and infrastructure projects
  • 2015On the market since 2015

Page updated . Written by the Zapple.Tech QA team.

What you can order

What can you order here? Four ways in, depending on where you are today.

iOS app test automation

Automated tests for native iOS apps that run on the simulators and devices agreed in the audit.

  • Core flows first, such as login, onboarding, purchase and upgrade
  • Accessibility identifiers agreed with your developers so locators stay stable
  • Tests run in your CI on every build or nightly

Android app test automation

Automated tests for native Android apps on the emulators and devices agreed in the audit.

  • The same flows as iOS, with one shared scenario where the apps behave alike
  • Platform-specific steps only where the apps differ
  • Results in the tools your team already reads

Cross-platform and hybrid app automation

Tests for apps that mix native screens and web views, and for cross-platform apps built on one codebase.

  • Switching between native and web view contexts inside one scenario
  • Mobile web on real mobile browsers; desktop-browser checks stay with web test automation
Web application testing

Mobile suite maintenance

When the app, the OS or a screen changes, tests break. We repair them and sort every red run.

  • Failures sorted into defects, test faults and device or environment faults
  • Flaky tests listed by device and OS version until they are fixed or removed
  • Repairs shown as a diff and reviewed before they are merged
Test maintenance

How it works

One mobile test scenario across the agreed device matrix

One mobile test scenario across the agreed device matrixOne scenario, written once, with platform-specific steps only where the iOS and Android apps differ, fans out to two platforms. On iOS it runs on simulators, real devices and a device cloud. On Android it runs on emulators, real devices and a device cloud. Which devices and OS versions are covered, and where each run happens, is agreed in the audit and written into the quote. No matrix covers every device your users own.One scenarioWritten once;platform-specific stepsonly where the appsdifferiOSSimulatorReal deviceDevice cloudAndroidEmulatorReal deviceDevice cloudThe device and OS matrix is agreed in the audit and written intothe quote. No matrix covers every device.One mobile test scenario across the agreed device matrixOne scenario, written once, with platform-specific steps only where the iOS and Android apps differ, fans out to two platforms. On iOS it runs on simulators, real devices and a device cloud. On Android it runs on emulators, real devices and a device cloud. Which devices and OS versions are covered, and where each run happens, is agreed in the audit and written into the quote. No matrix covers every device your users own.One scenarioWritten once; platform-specific steps onlywhere the apps differiOSSimulatorReal deviceDevice cloudAndroidEmulatorReal deviceDevice cloudThe device and OS matrix is agreed in the audit andwritten into the quote. No matrix covers everydevice.
How one mobile test scenario runs across iOS and Android on the device and OS matrix agreed in the audit, on simulators or emulators, real devices and a device cloud.

What we automate

Automated mobile app testing starts with the flows of your app that people use and that cost you when they break. That covers four kinds of app.

Native iOS apps

Screens built with Apple’s frameworks, tested on simulators and on devices, as agreed in the audit. Locators rely on accessibility identifiers that your developers add, because those rarely change when a screen is redesigned.

Native Android apps

The same flows, tested on emulators and devices. Where the iOS and Android apps behave the same way, one scenario serves both. Platform-specific steps are written only where the apps differ.

Cross-platform and hybrid apps

Apps built on one codebase, and apps that mix native screens with web views. A scenario can switch into the web view, check it and come back. See web test automation for sites in desktop browsers; mobile web in mobile browsers stays on this page. For the services behind the app, see API test automation. Every platform and test type is listed under test automation services.

Mobile web

A website opened in a mobile browser on a phone or tablet is a mobile test. Responsive checks in a desktop browser are not.

Devices: real, emulated and in the cloud

Device fragmentation is what makes mobile test automation services different from web testing. Phones and tablets differ by screen size, OS version, manufacturer and settings, and your users have all of them. The audit fixes the device and OS matrix with you: which devices and versions, which of them are emulators or simulators, which are real devices and which run in a device cloud. The matrix is written into the quote, including what it does not cover. No matrix covers every device your users own.

A device cloud you already have an account with can be used. Where each run happens is decided in the audit.

Frameworks and CI

Tools are chosen for your app. Appium is the common choice for tests that drive native and hybrid apps on iOS and Android.

CodeceptJS writes mobile tests as user steps. Its documentation says it allows you to test mobile and hybrid apps in a similar manner as web applications, runs the tests with Appium on emulated or physical devices, and shows a sample test that works on both iOS and Android, with separate locators per platform where needed. Inside a hybrid app it can run commands in the context of a web view. Zapple.Tech was founded by the founders of CodeceptJS and Codeception. If your web and mobile suites should read the same way, that is a reason to consider it. If your team already has Appium tests or native UI tests, we start from those. See CodeceptJS support.

Tests live in your repository and run in your CI/CD pipeline on every build or nightly, as agreed in the audit, and regression results reach the tools your team reads. Looking for a comparison of tools instead? Read our comparison of ten iOS app testing tools.

What to automate first, and what stays manual

Automate the flows where a failure costs most:

  • login and account creation
  • onboarding
  • purchase and payment screens
  • upgrade and migration paths

For a step-by-step start, see how to get started with mobile app testing automation.

Leave to people what a person judges better than a script: usability, how gestures feel, interruptions such as calls and low battery, and the first run on a new device. For those, see AI-assisted manual testing. A good mobile test strategy uses both.

Where AI helps in mobile test automation, and where it does not

AI agents can draft a test from a plan we agree with you, propose a repair when a locator or a screen changes, and group failures that look alike. Engineers review each change before it is merged, and a draft is run on the agreed matrix before anyone trusts it. For the same way of working on web applications, see end-to-end testing with AI agents. If your app was itself built with AI coding assistants, see QA for AI-generated code.

What AI does not do here: decide which flows matter, replace real-device checks, or make the tests right on its own. The limits below say more.

How the work runs

Inside the pilot the work follows five steps.

  1. Review the specifications and the flows picked in the audit.
  2. Select the devices on the agreed matrix.
  3. Write test cases and suites for the flows.
  4. Execute them in your CI.
  5. Analyse results: every red run is sorted into defect, test fault or device or environment fault.

Cooperation can take the form of full project outsourcing (see QA outsourcing), a dedicated QA team, or engineers joining your team: see hire mobile test automation engineers. To add people who test each build by hand, see hire mobile app testers. Prices are not published; a scoped quote arrives within one business day.

Honest limits

What mobile test automation does not solve. Automation makes repeated checks cheap. It does not remove the need for devices, people or judgement.

  • 01

    Tests on emulators miss problems that only appear on real hardware, such as memory pressure and camera or sensor behaviour. Some checks stay on devices.

  • 02

    A device matrix covers the devices agreed, not every device your users own. The quote says what it leaves out.

  • 03

    Animations, push notifications and OS permission dialogs make mobile tests slower and more fragile than web tests, so the suite stays focused on core flows.

  • 04

    An AI draft of a mobile test that passes on one device has not shown that it passes on the others. An engineer reviews it and it is run on the agreed matrix before it is merged.

  • 05

    App store review and staged rollouts are outside what tests control.

Compare the options

The four kinds of mobile app the page covers, what is tested and what is specific to each.

The four kinds of mobile app the page covers, what is tested and what is specific to each.
App kindWhat is testedWhat is specific
Native iOSScreens built with Apple's frameworks, on simulators and devices agreed in the auditLocators use accessibility identifiers that your developers add
Native AndroidThe same flows, on emulators and devicesOne scenario serves both apps where they behave alike; platform steps only where they differ
Cross-platform and hybridApps built on one codebase, and apps that mix native screens with web viewsA scenario can switch into the web view, check it and come back
Mobile webA website opened in a mobile browser on a phone or tabletCounts as a mobile test; responsive checks in a desktop browser do not

How the work runs

How does the work start? With the mobile test audit: about one week. You decide after each step whether to continue.

  1. About one week

    Mobile test audit

    We review your app, your specifications and any tests you have, and rank the flows by business risk. The device and OS matrix is fixed before any test is written.

    • App flows ranked by business risk
    • Device and OS matrix, with what it excludes
    • Recommended framework (Appium, CodeceptJS, or the native UI tests your developers already have) and where the tests will run
  2. Two to six weeks

    Pilot

    One or two critical flows are automated on iOS and Android and run in your CI on the agreed devices or device cloud.

    • Tests for those flows in your repository and CI
    • Results per device on the agreed matrix
    • A handover session on running the suite against your devices and builds
  3. Monthly

    Ongoing

    Zapple.Tech engineers extend coverage with each release, sort failures and repair broken tests, alongside your team.

    • Coverage extended each release
    • Failures sorted into defects, test faults and device or environment faults
    • Monthly report on coverage and flaky tests

Each step has a defined scope, duration and deliverables. You decide after each one whether to continue.

Tell us which platforms your app runs on, which flows must never break, and what you test with today, if anything. We reply within one business day with scope, timeline and a quote.

An engagement can start within two weeks of your go-ahead.

Client words

What clients say about working with us.

More than 50 testimonials
  • “Zappletech have provided us with software development and test automation services, both in terms of guiding the architecture, and implementing a lot of test case.”

    Chris McVittieHead of Technology, UK

Mobile test automation: your questions answered

What is mobile test automation?

Mobile test automation means scripts that drive your app on emulators, simulators or real devices and check the result, so the same flows can be re-run on every build without a person tapping through them. It is good at regression checks of core flows. It does not replace a person judging usability.

Which kinds of mobile apps can you automate?

Native iOS apps, native Android apps, hybrid apps with web views, cross-platform apps, and web apps in mobile browsers on phones and tablets. The audit confirms which of these your app is and how each part is tested.

Which frameworks do you use for mobile test automation?

Your stack comes first. Appium is the usual base for native and hybrid apps. CodeceptJS runs mobile tests through its Appium helper, and Zapple.Tech was founded by the founders of CodeceptJS and Codeception. If your developers already have native UI tests, the audit says whether to build on them. The choice is written into the audit report.

Do you test on real devices, emulators or a device cloud?

The mix is agreed in the audit. The device and OS matrix goes into the quote, including what it does not cover. If you already have a device cloud account, it can be used; otherwise the audit recommends where the tests will run.

How do you handle iOS and Android differences?

One scenario is shared between the platforms where the app behaves the same, and platform-specific locators or steps are written only where it does not. CodeceptJS can take separate locators for Android and iOS inside the same step.

What makes mobile apps harder to automate than web apps?

Device fragmentation (screen sizes, OS versions, manufacturers), OS permission dialogs, push notifications, animations and unreliable networks. Each adds waiting and branching to a test, so a mobile suite stays focused on core flows and runs on an agreed matrix rather than on every device.

What should we automate first, and what should stay manual?

Automate the flows that earn or lose money first, such as login, onboarding, purchase and upgrade. Usability, the feel of gestures, interruptions and first-run checks are often better left to people. For those, see AI-assisted manual testing.

How do mobile tests run in our CI?

The tests live in your repository and run in your CI/CD pipeline, on every build or nightly, whichever the audit recommends. Results appear in the tools your team already uses.

How long until the first tests run?

The audit takes about a week. The pilot takes two to six weeks. Access to builds, the state of your test data and the devices agreed decide where in that range it lands.

Who does the work, and what do we keep if we stop?

Zapple.Tech test automation engineers, working in your repository and CI. Team size is set in the quote, and term and notice are in the contract. The tests stay in your repository as ordinary code, and the pilot ends with a handover session for your engineers.

Can AI write or fix our mobile tests, and what does it see?

An AI agent can draft a test from a plan or propose a repair when a locator changes. An engineer reviews the change before it is merged, and the draft is run on the agreed devices. Only AI tools you approve are used, and which builds, accounts and test data they may see is agreed before the start.

How much does mobile test automation cost?

Prices are not published. The quote depends on the platforms, the number of flows, the device matrix and the state of any existing suite. Describe the app and you get a scoped quote within one business day.

Request a mobile audit quote

Tell us what you ship and what worries you.

What happens after you send this

  1. You send the form: your situation and what you need tested, then your name and work email.
  2. Within one business day, we reply with a suggested first step, its scope, timeline and a quote.
  • Fixed scope
  • You decide after each step
  • The tests live in your repository
  • An NDA signed before access

“They helped us to close the positions and consult our team how to proceed further. High-quality quick feedbacks with the deep checking of the required tasks, professional approach, great understanding of the company's technologies and product, detailed reports.”

Kristina Lavrentieva, Manager at keepgo.com, Israel
  • Rated 4.9 out of 5 on Clutch, from 7 client reviews
  • 42 completed test automation and infrastructure projects
  • Founded by the founders of CodeceptJS and Codeception, open-source testing frameworks

Request a QA audit quote

    What is closest to your situation?
    Optional. The product, the platforms, how often you release, what broke last.

    You decide after our reply whether to go ahead.

    Prefer to talk first? Book a call

    One-week QA audit · written report

    Request a mobile audit quote