Mobile testing is its own discipline.
Mobile testing scope:
- Salesforce Mobile App (most users).
- Field Service Mobile App (field technicians).
- Custom mobile apps (Mobile SDK).
- Mobile web access (browser).
Approaches:
1. Manual device testing.
- Real devices: iPhone, Android, various models, sizes.
- iOS / Android versions: latest + 1-2 prior.
- Different network conditions: WiFi, 4G, offline.
2. Emulator / simulator testing.
- iOS Simulator (Xcode).
- Android Emulator.
- Cheaper than real devices for breadth.
- Limited for some features.
3. Cloud device labs.
- BrowserStack, Sauce Labs, AWS Device Farm.
- Hundreds of device-OS combinations.
- Automated test runs.
4. Automated mobile testing.
- Appium — generic mobile automation.
- Provar / Tosca — Salesforce-aware mobile testing.
- Detox — for custom React Native apps.
Test scenarios:
1. Layout and rendering.
- Lightning Record Pages adapt to phone form factor.
- Compact Layouts render correctly.
- Touch targets large enough.
2. Navigation.
- Tab switching, swipes, gestures.
- Deep linking.
- Back-button behavior.
3. Data entry.
- Forms, picklists, lookups.
- Date/time pickers.
- Camera / photo upload.
4. Performance.
- Page load on cellular.
- Battery consumption.
- Memory usage.
5. Offline.
- Briefcase functionality.
- Sync when online.
- Conflict resolution.
6. Notifications.
- Custom Notifications received.
- Push notification delivery.
- Tap behavior.
7. Auth.
- MFA on mobile.
- SSO from mobile.
- Touch ID / Face ID.
Common pitfalls:
- Testing on desktop only — mobile-specific issues missed.
- One device — others have different behavior.
- No real-device testing — emulators miss real-world issues.
- Old OS only — new OS releases break things.
- Best-network testing — cellular issues missed.
Senior QA insight: mobile is a real testing surface, not an afterthought.
The senior framing: Salesforce Mobile is many users' primary access. Test thoroughly.