Testing for app interactions
We test how your mobile app behaves when it meets the rest of the device: notifications, permission prompts, deep links, app switching, incoming calls and low battery. We test on iOS and Android, using the situations your users actually hit.
What we interrupt your app with
- NotificationsPush, local, badges
- PermissionsGrant, deny, revoke
- InterruptionsCalls, SMS, low battery
- App switchingBackground and back
What is testing for app interactions?
Testing for app interactions checks how a mobile application behaves when it interacts with device hardware, operating system services and other installed applications.
This covers notifications, permission requests, deep links, multitasking and interruptions such as incoming calls or low battery warnings. iOS and Android handle each of these differently, so each platform needs its own test cases.
Interaction types
| Interaction type | Description | Scope |
|---|---|---|
| Notifications | Push notifications, local alerts, notification actions, badges, sounds and Do Not Disturb, on iOS and Android. | Cross-platform |
| Permissions | Camera, location, microphone, contacts and storage requests, denials and runtime changes, with a sensible fallback each time. | Security |
| Deep links | Universal links (iOS) and app links (Android) that open the right screen from emails, web pages or other apps. | Navigation |
| App switching | State is kept when users switch apps, return from the background or use split-screen. | Multitasking |
| Background/foreground | Lifecycle transitions, saved data, background tasks and network requests as the app changes state. | Lifecycle |
| Interruptions | Phone calls, SMS, low battery warnings, system updates and alarms that pause the app. | Resilience |
Interaction testing process
Identify integration points
Map every device API, OS service and third-party app your application depends on or talks to.
Platform-specific scenarios
Write test cases for iOS behaviours (universal links, review prompts) and Android ones (intents, back button navigation).
Interruption simulation
Trigger incoming calls, SMS, low battery, memory warnings and system dialogs, and check the app recovers its state.
Permission workflows
Test when permissions are requested, what happens on denial, the redirect to settings and changes made while the app runs.
Cross-device validation
Run the tests on several device types, OS versions and manufacturers to catch fragmentation problems.
Why test app interactions?
Prevent crashes
Interruptions are where many apps lose state or crash. Testing lifecycle transitions and resource cleanup finds those failures first.
We check: incoming call handling, memory pressure scenarios, background task termination, state restoration failures.
Platform compliance
App stores can reject apps that mishandle permissions or break platform guidelines. We test against the iOS and Android rules.
We check: permission request timing, background location usage, App Store review requirements, privacy manifest declarations.
User trust
Users drop apps that behave oddly during interruptions or ask for too many permissions.
We check: clear permission requests, graceful degradation, data persistence, predictable navigation.
OS fragmentation
Android device variety and the spread of iOS versions mean the same code behaves differently across phones.
We check: permission model changes, background execution limits, API deprecations, device-specific quirks.
Industry standard
Based on ISTQB mobile testing
This page follows the ISTQB Mobile Application Testing syllabus, which treats testing for app interactions as a core part of mobile testing: platform behaviours, interruption handling and lifecycle management on iOS and Android.
The wider picture is on our mobile app testing page, and service-to-service checks on API testing and integration testing.
How BetterQA does app interaction testing
We test your app on the iOS and Android versions your users run, on real devices through BrowserStack, plus any devices you ask us to include, interrupt it the way real life does, and report each failure with the device, OS version and steps.
Engineers who test for a living
BetterQA, founded 2018, 50+ QA engineers. People plan and run the app interaction testing and report what the results mean for your release.
Bugs you can act on
Every defect we find is written up in BugBoard, our own test management tool, or in your tracker, with steps to reproduce, the expected and actual result, and the environment.
A certified process
ISO 9001 for quality management and ISO 27001:2022 for information security. See our certifications.
How an engagement works
- €20-45 per hour
- First month is a trial
- First two weeks complimentary if you are not happy
- 30 days' notice after that
App interaction testing: common questions
What is testing for app interactions?
Testing how a mobile app behaves with the device around it: notifications, permissions, deep links, app switching, background states and interruptions.
What is interruption testing in mobile apps?
Checking that the app survives and recovers from calls, messages, alarms, low battery and system dialogs without losing the user's work.
How do you test interactions with third-party apps?
We map the apps and services yours talks to, such as maps, payments or sharing, and test each hand-off in both directions, including when the other app is missing.
Do iOS and Android need separate interaction tests?
Yes, for many cases. Permissions, deep links and background limits work differently on each platform, so a shared test plan has platform-specific cases.
What does it cost?
The cost depends mostly on how many platforms and OS versions you need covered. Our rate is €20-45 per hour. For ongoing work the first month is a trial, the first two weeks are complimentary if you are not happy, and after that it is 30 days' notice.
Need mobile interaction testing?
Send us your app build. We will interrupt it the way your users' phones do and show you where it loses state or crashes.