Assessment Overview
Congratulations on reaching the end of Module 7: Mobile Testing. This assessment tests your understanding of all topics covered in lessons 7.1 through 7.24.
The assessment has three parts:
| Part | Format | Questions | Time Estimate |
|---|---|---|---|
| Part 1 | Multiple-choice quiz | 10 questions | 10 minutes |
| Part 2 | Scenario-based questions | 3 scenarios | 15 minutes |
| Part 3 | Practical exercise | 1 exercise | 20 minutes |
How to Use This Assessment
Before you begin:
- Review your notes from Module 7
- Do not use reference materials during the quiz (Part 1)
- For Parts 2 and 3, you may reference earlier lessons
Scoring guide:
- Part 1: 10 points (1 point per correct answer)
- Part 2: 15 points (5 points per scenario)
- Part 3: 15 points (rubric provided)
- Total: 40 points
- Passing score: 28/40 (70%)
Topics Covered
- Platform fundamentals — iOS vs Android, native/hybrid/cross-platform
- Device lab — Physical devices, cloud farms, device selection strategy
- Platform specifics — iOS lifecycle, Android Activity lifecycle, manufacturer differences
- UI/UX testing — Touch targets, gestures, responsive layouts
- Connectivity — Network conditions, offline mode, synchronization
- Push notifications — Delivery, display, deep linking, permissions
- Deep links — Universal links, app links, deferred deep links
- Performance — Battery, memory, storage, profiling
- Security — Data storage, network security, biometric authentication
- Crash analytics — Crashlytics, Sentry, symbolication
- Monetization — In-app purchases, subscription testing
- Extended platforms — CarPlay, Android Auto, wearables
- Quality — A/B testing, distribution, accessibility, localization
Part 1: Multiple-Choice Quiz
The quiz questions are in the frontmatter of this lesson (10 questions). Take the quiz first before proceeding to Parts 2 and 3.
Part 2: Scenario-Based Questions
Scenario A: Cross-Platform Launch
Context: Your company is launching a new fitness app simultaneously on iOS and Android. The app uses GPS tracking, camera (for food logging), push notifications, and in-app purchases. You have 3 weeks for testing, a team of 4 testers, and a budget of $5,000 for devices and tools.
Questions (5 points):
- Design your device test matrix (which devices, why). (2 points)
- What are the top 3 platform-specific risks and how would you test for them? (3 points)
Solution
1. Device matrix: iPhone 15 (iOS 17, flagship), iPhone 12 (iOS 16, older model), Samsung Galaxy S24 (Android 14, top Android), Samsung Galaxy A54 (Android 13, mid-range), Google Pixel 8 (Android 14, stock Android). Plus BrowserStack for extended coverage. Total: ~$3,500 devices + $1,500/year cloud farm.
2. Top 3 risks: (a) GPS accuracy differences between iOS Core Location and Android Fused Location Provider — test in real outdoor conditions on both platforms; (b) Background push notification delivery on Xiaomi/Samsung where aggressive battery optimization kills background processes — test with OEM power settings; (c) In-app purchase testing with sandbox environments on both App Store and Google Play — test all purchase flows, restoration, and subscription management.
Scenario B: Production Crash Investigation
Context: After a release, Crashlytics shows a 3% crash rate on Samsung devices running Android 13. The crash occurs in the photo upload feature.
Questions (5 points):
- What information from Crashlytics would you analyze first? (2 points)
- How would you reproduce and investigate this crash? (3 points)
Solution
1. Crashlytics analysis: (a) Stack trace — identify the exact code line and exception type; (b) Device distribution — which Samsung models are affected; (c) OS version — confirm it is Android 13 specific; (d) App version — confirm it started with the latest release; (e) User actions before crash (breadcrumbs).
2. Reproduction: (a) Get a Samsung device with Android 13; (b) Follow the breadcrumb trail from Crashlytics; (c) Test photo upload with various photo sizes, formats, and camera sources; (d) Check Samsung-specific camera API behavior; (e) Test with different One UI versions; (f) Use ADB logcat to capture detailed crash logs.
Scenario C: Accessibility Audit
Context: Your app must achieve WCAG 2.1 AA compliance for mobile. A screen reader audit reveals that 40% of screens have navigation issues with VoiceOver/TalkBack.
Questions (5 points):
- What are the three most common mobile accessibility issues? (2 points)
- Design a remediation plan with priorities. (3 points)
Solution
1. Common issues: (a) Missing accessibility labels on images, buttons, and icons; (b) Incorrect reading order that does not match visual layout; (c) Touch targets smaller than 44x44 points that are difficult for motor-impaired users.
2. Remediation plan: Priority 1 (week 1): Fix all missing labels on interactive elements (buttons, inputs, links) — these block navigation. Priority 2 (week 2): Fix reading order on critical flows (login, checkout, main navigation). Priority 3 (week 3): Fix touch target sizes, color contrast, and Dynamic Type support. Verification: Full VoiceOver/TalkBack walkthrough of all fixed screens, automated scan with axe-core.
Part 3: Practical Exercise
Design a Mobile Test Strategy
Scenario: You are the QA Lead for a ride-sharing app (like Uber). The app has:
- Real-time GPS tracking for drivers and riders
- Payment processing (credit card, Apple Pay, Google Pay)
- Push notifications for ride updates
- In-app messaging between driver and rider
- Rating and review system
- Multi-language support (10 languages)
- 5 million monthly active users (60% Android, 40% iOS)
Design a mobile test strategy that includes:
- Device matrix with justification
- Top 5 mobile-specific test areas ranked by risk
- Automation strategy for mobile testing
- Network and offline testing approach
- Performance testing targets
Scoring rubric (15 points):
| Criterion | Points |
|---|---|
| Device matrix quality | 3 |
| Risk assessment accuracy | 3 |
| Automation strategy practicality | 3 |
| Network testing completeness | 3 |
| Performance targets realism | 3 |
What is Next
If you scored 28+ out of 40, you are ready for Module 8: Test Automation. If you scored below 28, review the topics where you lost points before proceeding.