Kordant/tasks/android-production/04-internal-testing.md

04. Internal Testing Track

meta: id: android-production-04 feature: android-production priority: P1 depends_on: [] tags: [play-store, testing, production]

objective:

• Set up internal testing track with 20+ testers to validate app before public release

deliverables:

• Internal testing group with 20+ testers
• Testing feedback process
• Automated crash reporting
• Iteration cycle

steps:

1. Create internal testing track:
   • In Play Console → Testing → Internal testing
   • Add team members and trusted testers by email
   • Target 20-100 testers
   • Include various Android versions and devices
2. Upload first test build:
   • Generate signed AAB
   • Upload to internal testing track
   • Add release notes
   • Publish to internal testers
3. Prepare testing materials:
   • Test invitation email template
   • Testing checklist and focus areas
   • Feedback collection form or channel
   • Known issues list
4. Set up crash reporting:
   • Integrate Firebase Crashlytics
   • Enable NDK crash reporting if using native code
   • Configure alerts for crash spikes
   • Link crashes to specific builds
5. Collect and triage feedback:
   • Review Play Console tester feedback
   • Monitor Crashlytics for crashes
   • Create issues from feedback
   • Prioritize critical bugs
6. Iterate:
   • Fix critical bugs within 1 week
   • Upload new builds every 1-2 weeks
   • Track tester retention and engagement
   • Expand to closed testing after internal validation
7. Prepare for closed testing:
   • Create closed testing track
   • Plan external tester recruitment
   • Prepare onboarding flow for new testers

tests:

• Distribution: Testers receive and install build
• Feedback: Feedback collection channel active
• Crash: Crash reporting receiving reports

acceptance_criteria:

• Internal testing track with 20+ testers
• First build uploaded and distributed
• Testers can install and run app
• Crash reporting active and receiving data
• Feedback collection process defined
• Known issues documented and shared
• New builds uploaded every 1-2 weeks
• Zero critical crashes in last 2 builds
• Closed testing track prepared
• Testers cover range of Android versions (10-14)

validation:

• Testers receive email invite → install app
• Run app → no immediate crashes
• Submit feedback → received by team
• Simulate crash → appears in Crashlytics
• Upload new build → testers receive update

notes:

• Internal testing is immediate (no review)
• Closed testing requires Google review (may take days)
• Use Firebase App Distribution for faster iteration if needed
• Test on physical devices, not just emulators