Mobile app testing
Mobile testing at TestLine means checking your app on iOS and Android, manually on real devices and automatically with Appium, XCUITest or UIAutomator. Among others, I've tested a bank's mobile app used by hundreds of thousands of customers.
- Appium
- XCUITest
- UIAutomator
- iOS
- Android
What you get
- A device and OS version matrix based on your users
- Functional, permission, notification, offline and update testing
- Automation of critical paths in Appium, XCUITest or UIAutomator
- Log analysis (Logcat, Xcode console) attached to bug reports
When it's worth it
Before store submission
An App Store rejection or a crash after launch costs more than testing before release.
When it only works on one phone
The team tests on their own devices. I'll check the app on emulators with other screens and OS versions.
For apps with payments
Login, payments and personal data need thorough testing of error paths.
With frequent updates
Automated regression lets you ship without clicking through everything again.
How I work
- step 1
Scope
We agree on OS versions and priority scenarios.
- step 2
Testing
Manual tests on devices and emulators.
- step 3
Automation
Scripts for critical paths, running in CI.
- step 4
Report
Results per platform and a recommendation before publishing.
Tools
- Appium
- XCUITest
- UIAutomator
- iOS
- Android
Frequently asked questions
Do you test native and hybrid apps?
Yes. Native (Swift, Kotlin) and apps built with React Native or Flutter. I choose automation tools to match the technology.
What do you test on?
Emulators and the physical devices I have. If a specific model matters to you, let me know when we agree on the scope.
What do I need to prepare for testing?
An app build and test data, such as user accounts.
Got a release in a few weeks?
Describe your project in the form. I'll reply with questions about scope or an initial test plan.