Make runtime verification reproducible.
1. Device selection
Identify the intended emulator or physical device explicitly, especially when several are connected. Record OS and device characteristics with the result.
2. Install and launch
Treat installation, launch and app readiness as separate steps. A successful APK install does not prove the app starts or reaches the target screen.
3. Runtime evidence
Collect focused logs and interaction evidence for the requested behavior. Avoid dumping unrelated user data or claiming success from an empty crash log alone.
Worked scenario
The app installs but crashes before its first screen. The deployment step succeeded while the product verification failed.
Apply it
Deploy a debug build, navigate to one feature and capture an observable success and failure case.
Check your understanding
Your report identifies the exact build, device and behavior verified. Explain the decision and show evidence from your implementation or design. If you cannot demonstrate it yet, revisit the relevant section before continuing.