Scoopd QA Playbook
qaThis file extends _skill.md — load that first for environment setup, build commands, and mobile-mcp tool reference. Verify scoopd dev-client builds on the Android emulator and exercise user flows via mobile-mcp. File bugs in Jira project HOME at aictpo.atlassian.net using mcp__atlassian__* tools. Before any test session: Confirm emulator is up/opt/android-sdk/platform-tools/adb devices -lExpect emulator-5554 device. If missing, the emulator needs to be relaunched (out of scope for QA — escalate).Confirm a build is installed/opt/android-sdk/platform-tools/adb shell pm list packages | /system/bin/grep com.aictpo.scoopdExpect package:com.aictpo.scoopd. If missing, build first: cd ~/oss/scoopd/apps/mobile && npx expo run:android.Confirm Metro is running (if testing dev client)curl -sf http://localhost:8081/status | grep -q "packager-status:running" && echo OKIf not running, dev client will hang at the splash screen. Restart with npx expo start --dev-client from apps/mobile/.Reset app state for a clean session/opt/android-sdk/platform-tools/adb shell pm clear com.aictpo.scoopd /opt/android-sdk/platform-tools/adb shell am start -n com.aictpo.scoopd/.MainActivityGet test credentials from agent memory — they are NOT in this skill pack. Check ~/.claude/projects/-home-agent-workspace/memory/ for scoopd_test_creds.md. If absent, ask the operator. Verify topResumedActivity is com.aictpo.scoopd/.MainActivitymobile_take_screenshot — confirm Sign In screen rendersCheck logcat for FATAL errors:/opt/android-sdk/platform-tools/adb logcat -d -t 200 | /system/bin/grep -iE "fatal|reactnativejs.*error" Pass criteria: App reaches Sign In screen within 30s of launch with no FATAL errors. mobile_list_elements_on_screen → get coordinates of Email fieldmobile_click_on_screen_at_coordinates to focus Emailmobile_type_keys with the test emailmobile_list_elements_on_screen again (re-render may have shifted layout)Tap Password field, type the passwordTap Sign In buttonWait for navigation, screenshot every 2s up to 10sVerify post-login screen renders (logged-in landing screen) Pass criteria: User reaches the post-login landing screen. No error toast/banner.