Section 4 Review

Section 4 closed the toolkit: extending existing performance and security disciplines to mobile's device-side layer, then adding systematic crash investigation for defects that only surface in production.

Knowledge Check

Work through these five scenarios before checking the Section 4 Solutions.

Scenario 1: The Sluggish App

Server-side response times for a mobile app's API are consistently fast, but users report the app feeling sluggish after extended use. What layer of testing would investigate this, and what specific measurement would you take?

Scenario 2: Where's the Token?

A mobile app's login, lockout, and session-timeout behavior all pass their tests correctly. What mobile-specific security check might still be missing, and why does it matter?

Scenario 3: Trust, but Verify

A QA engineer assumes the mobile app's certificate pinning works correctly because it was implemented by the development team. What should they do instead, and why?

Scenario 4: The Unreproducible Crash

A tester attempts to reproduce a crash report on the first available test device, fails, and marks it "can't reproduce." What should have happened before that reproduction attempt?

Scenario 5: Background Cost

A rarely-used feature is found to have a disproportionate battery impact. What kind of activity is a likely cause, and how would you specifically test for it?

Next: Check your answers against the Section 4 Solutions, then continue to Section 5 — Application Modules.