Phase 7Days 35-39

Testing, Debugging & Mobile Security

Unit, component, integration, E2E, native diagnostics, secrets, storage, and hostile-input thinking

Phase Goal

Prove critical behavior across platforms and protect user data against realistic mobile threats.

Progress

Day 35: Unit & Component Tests

Day 36: Integration & End-to-End Mobile Tests

Day 37: Debugging Native-Shaped Failures

Day 38: Mobile Security & Privacy

Day 39: Mini Project — Youth Club Consent Desk

Capstone
Youth Club Consent Desk

Build a staff-facing consent-status app that answers only whether a participant may join a selected activity. Store the minimum metadata, gate staff access with platform authentication, redact sensitive screens when backgrounded, and state clearly what a rooted or jailbroken device can still expose.

  • SecureStore-backed session material, biometric/passcode policy, timeout, redaction, and safe sign-out
  • Validated deep links, redacted logs, hostile server payload handling, and privacy-safe analytics boundaries
  • Layered tests covering expiry, denial, backgrounding, malformed links, offline state, and release-only behavior
  • Transfer: handle a lost-device report by revoking the mock session and proving cached private views are inaccessible

Phase Complete!

After this phase, you'll be able to:

  • Behavior-first test boundaries
  • Jest preset, pure logic, timers, and deterministic tests
  • React Native Testing Library queries and user events
  • Accessibility assertions and avoiding implementation coupling
  • Navigation, Redux, network, and persistence integration harness
  • Mock server boundaries and failure scenarios
  • Maestro/Detox E2E trade-offs and stable selectors
  • Device matrix, permissions, deep links, and flaky-test control

You can apply Phase 7 skills in a tested mobile project on Android and iOS.