Key Considerations for Mobile App Testing

1. Clarify Devices and Platforms Before Starting

At the beginning of test design, testers determine the devices and platforms the app will run on, predicting user devices for new apps and covering various OS versions and screen sizes, especially high‑market‑share versions.

2. Consider User Mobility and Network Variability

Testers must not assume user habits; because apps are mobile, they should be tested under weak network, no network, airplane mode, and network switching scenarios.

3. Account for Multitasking and Unexpected Situations

Testing should include handling of incoming calls or messages, app switching, media playback interactions, headphone plug/unplug, Home button, lock/unlock effects.

4. Check for Gesture Conflicts

If the app uses gestures, ensure they do not conflict with system gestures.

5. Focus on User Experience

Beyond functional requirements, test non‑functional aspects such as orientation changes, font scaling, inverse colors, zoom, and accessibility features like VoiceOver.

6. Verify Permissions, Notifications, and Message Display

Ensure the app clearly declares required permissions to avoid rejection from app stores, and consider status bar, lock‑screen notifications, and related UI changes.

7. Ensure Timely Message Display and Synchronization

Test caching mechanisms (memory, file, CDN) and verify that messages appear correctly under various conditions, reducing network load and improving stability.

8. Reduce Dependency on Existing Web Versions

Avoid over‑reliance on web implementations when the app merely wraps web content.

9. Conduct Layered and Exploratory Testing

Early testing lowers bug‑fix costs; exploratory testing encourages creative test paths beyond conventional scripts.

10. Perform App Security Testing

Check for plaintext user data, ensure request encryption, secure SQLite storage, and use tools for security assessment.

11. Leverage Logs for Issue Analysis

Record errors and important actions in logs, possibly providing a log‑upload entry for user feedback.

Source: Based on the book “22 Rules of Mobile App Testing”.