01 What is Mobile Testing?
What's genuinely different about testing a mobile app versus a web or API surface — device fragmentation, platform constraints, and mobile-specific failure modes no prior TestAtlas path covers.
02 Android vs. iOS Testing
The genuine platform differences a mobile tester needs to account for — permission models, navigation conventions, distribution and lifecycle behavior — taught as practical testing differences, not OS internals.
03 Mobile Device Ecosystem
The real scope of device fragmentation a mobile tester has to reason about — screen size, OS version, and manufacturer customization — and why testing a few devices isn't the same as testing the device landscape.
04 Installation and Upgrade Testing
Testing fresh install, upgrade-from-a-prior-version, and uninstall/reinstall paths — a mobile-specific testing surface with no direct web or API equivalent.
05 Mobile UI and Navigation Testing
Applying Boundary Value Analysis and Equivalence Partitioning to mobile-specific UI inputs — touch gestures, screen rotation, and soft keyboard behavior — rather than re-teaching test design from scratch.
06 Network, Interruptions, Offline
Testing behavior under interrupted, degraded, or absent connectivity — backgrounding mid-operation, offline queuing, and retry-on-reconnect — building on API Testing's own resilience and idempotency concepts.
07 Device Fragmentation
Systematically testing across the real device, OS-version, and manufacturer combination space, applying Combinatorial and Pairwise Testing directly rather than testing exhaustively or arbitrarily.
08 Sensors, Permissions, and Hardware
A single behavioral framework for testing any hardware capability — availability, permission state, runtime changes, and recovery — instead of a device-by-device feature checklist.
09 Compatibility and Responsive Behavior
Testing that functionality (compatibility) and layout (responsive behavior) both hold up correctly across the pairwise-selected device set, as two related but distinct checks.
10 Mobile Performance Testing
Applying the existing performance-testing toolkit — metrics, test types, bottleneck analysis — to mobile's specific constraints: battery, memory-limited devices, and variable network conditions.
11 Mobile Security Testing
Applying this path's established QA-level, identification-not-exploitation security scope to mobile-specific concerns: local storage encryption, certificate pinning, and insecure inter-app communication.
12 Crash Analysis and Logging
Systematic crash investigation for mobile apps — reproducing from a crash log, distinguishing device-specific from universal crashes, and closing Section 4's toolkit.
13 Applying Mobile Testing: AtlasBank Validation
Combining device coverage, hardware, connectivity, performance, security, and crash-analysis technique from Sections 1-4 against a realistic, integrated AtlasBank mobile fund-transfer feature.
14 Applying Mobile Testing: AtlasShop Validation
Combining installation, offline queuing, performance, and security technique from Sections 1-4 against a realistic, integrated AtlasShop mobile checkout and cart feature, contrasting with AtlasBank's transfer flow.
15 Common Mobile Testing Mistakes
Six mobile-testing mistake patterns spanning device selection, transitions, connectivity, hardware, layout, and performance/security — each traced back to a real defect earlier in this path.
16 Capstone: AtlasBank Mobile End-to-End Verification
The complete mobile-testing lifecycle applied to AtlasBank's International Money Transfer feature — verifying real-world device, connectivity, and interruption behavior on the same already-correct implementation five prior certified paths verified from their own layer.
Section 1 — Review
A recap of Mobile Testing Foundations — what's different about mobile, Android vs. iOS testing, and the real device ecosystem — plus a Knowledge Check.
Section 1 — Solutions
Answers and reasoning for Section 1's Knowledge Check — applying mobile-specific testing surfaces, platform differences, and device-selection criteria to five realistic scenarios.
Section 2 — Review
A recap of Functional Mobile Testing — installation and upgrade paths, mobile UI input surfaces, and connectivity interruption and offline testing — plus a Knowledge Check.
Section 2 — Solutions
Answers and reasoning for Section 2's Knowledge Check — applying installation/upgrade testing, mobile UI technique, and connectivity interruption testing to five realistic scenarios.
Section 3 — Review
Knowledge Check for Section 3 — Device Fragmentation, Sensors/Permissions/Hardware, and Compatibility and Responsive Behavior.
Section 3 — Solutions
Answers and reasoning for Section 3's Knowledge Check — applying pairwise device testing, the five-state hardware framework, and compatibility vs. responsive behavior to five realistic scenarios.
Section 4 — Review
Knowledge Check for Section 4 — Mobile Performance Testing, Mobile Security Testing, and Crash Analysis and Logging.
Section 4 — Solutions
Answers and reasoning for Section 4's Knowledge Check — applying mobile performance, security, and crash analysis to five realistic scenarios.