Section 2 Review
You've finished Functional Mobile Testing, the second section of Mobile Testing. This page is a dedicated recap — bookmark it as a fast reference, separate from the modules themselves.
Section Summary
✔ Installation and Upgrade Testing — fresh install, upgrade from a real prior version, and uninstall/reinstall as three distinct paths, each exposing risks the others can't ✔ Mobile UI and Navigation Testing — applying Boundary Value Analysis and Equivalence Partitioning directly to touch gestures, screen rotation transitions, and soft keyboard behavior ✔ Network, Interruptions, and Offline Testing — three distinct connectivity conditions, offline queuing, and retry-on-reconnect safety, building directly on API Testing's own idempotency and resilience techniques
How they build on each other: Module 4 established that how an app gets onto a device is its own testing surface. Module 5 applied existing test-design technique to how a user interacts with the installed app's UI. Module 6 closed the section with the highest-stakes mobile-specific risk — connectivity interruption — directly setting up the systematic device/platform testing Section 3 builds next, and this path's own eventual capstone.
Section 2 Quick Reference
| Question | What to Check |
|---|---|
| Does an app update correctly handle existing users' data? | Test upgrading from a real prior version (more than one back), not just a fresh install |
| Does a mobile UI handle rotation and gestures correctly? | Test the rotation transition mid-interaction; test distinct gesture types as separate equivalence classes |
| Is retry-on-reconnect safe from duplicate submissions? | Interrupt connectivity between request-sent and confirmation-received; verify the retry checks the actual outcome first |
Section 2 Knowledge Check
Five realistic scenarios. For each, decide which module's framework applies. No answers are provided here. Solutions: Section 2 Solutions.
Scenario 1: A release changes how local notification preferences are stored, and the team wants to know if existing users' settings survive the update correctly.
Scenario 2: A tester wants to verify that rotating the device while a multi-step form is partially filled doesn't lose entered data.
Scenario 3: A payment feature needs to be verified safe against submitting twice if connectivity drops right after the user taps "Pay."
Scenario 4: A team wants to know if a rapid double-tap on a "Submit" button could trigger two submissions.
Scenario 5: A team wants to test what happens to an action a user takes while their phone has no signal at all.
Continue to Section 3
Device and Platform Testing, starting with Device Fragmentation — where this section's foundational and functional coverage extends into systematic testing across the real device landscape Section 1 mapped.