Kordant/docs/android-testing/INTERNAL_TESTING.md

Kordant Android — Internal Testing Guide

Overview

This document describes the internal testing process for the Kordant Android app. It covers tester onboarding, testing checklists, feedback collection, and iteration cycles.

Play Store Internal Testing Setup

1. Create Internal Testing Track

1. Go to Google Play Console
2. Navigate to Testing → Internal testing
3. Create a new internal testing track
4. Add testers by email address

2. Internal Testing Group (Target: 20+ testers)

Add the following categories of testers:

Category	Count	Purpose
Engineering team	5-10	Core functionality validation
Product/QA	3-5	Feature verification
Design	1-2	UI/UX validation
External trusted	10+	Real-world device coverage

3. Device Coverage

Ensure testers cover these Android versions and device types:

Android Version	API Level	Priority
Android 14	34	High
Android 13	33	High
Android 12	32	Medium
Android 11	30	Medium
Android 10	29	Low

Device Type	Examples
Pixel	Pixel 6, 7, 8, Fold
Samsung	Galaxy S23, S24, Tab S9
Xiaomi	Redmi Note series
OnePlus	OnePlus 11, 12
Foldable	Pixel Fold, Galaxy Z Fold

Test Invitation Email Template

Subject: You're invited to test Kordant Android (Internal Testing)

Hi [Name],

You've been selected as an internal tester for the Kordant Android app.
Your feedback will help us ship a polished, production-ready app.

**What to test:**
- App installation and first launch
- Authentication (email/password + Google Sign-In)
- Dashboard and threat score display
- Service screens (DarkWatch, VoicePrint, SpamShield, etc.)
- Push notifications
- Call screening (SpamShield)
- Settings and preferences
- Offline behavior
- Performance (cold start, scrolling, animations)

**How to install:**
1. Click the link below to join the internal testing program
2. Open the Google Play Store on your Android device
3. Search for "Kordant"
4. Tap "Accept" to join as a tester
5. The app will appear in your Play Store — tap "Install"

[INSERT PLAY CONSOLE TESTING LINK]

**Testing period:** [START DATE] to [END DATE]

**How to report issues:**
- In-app: Use the feedback form in Settings
- Email: testing@kordant.ai
- Slack: #android-testing channel

Thank you for helping us build a great app!

The Kordant Team

Testing Checklist

Installation & First Launch

• App installs from Play Store without errors
• Cold start completes under 1.5 seconds
• Splash screen displays correctly
• No crashes on first launch

Authentication

• Email/password login works
• Email/password signup works
• Google Sign-In works
• Forgot password flow works
• Reset password flow works
• Biometric authentication (if enabled)
• Token refresh works silently
• Logout clears all data

Dashboard

• Threat score displays correctly
• Recent alerts load and display
• Service summary cards show correct counts
• Pull-to-refresh works
• Alert detail navigation works
• Service navigation works

Services

• DarkWatch screen loads watchlist
• VoicePrint enrollment works
• SpamShield rules display
• HomeTitle properties load
• RemoveBrokers listings display

Notifications

• Permission dialog shows on first launch (Android 13+)
• Push notifications display correctly
• Notification deep links route to correct screen
• Different notification priorities display correctly

Security Features

• Certificate pinning active (check logs)
• Encrypted storage for sensitive data
• Root detection works (test on rooted device)
• Permissions have rationale dialogs

Performance

• Cold start under 1.5s on Pixel 6
• No ANRs when scrolling large lists
• Image loading is smooth
• Background sync doesn't drain battery

Accessibility

• TalkBack reads all interactive elements
• All icons have content descriptions
• Color contrast meets WCAG AA
• Font scaling works up to 200%

Offline Behavior

• App works without network
• Cached data displays when offline
• Queue shows pending requests
• Sync resolves when network returns

Feedback Collection

Channels

1. Play Console Feedback: Testers can leave feedback directly in Play Store
2. In-app Feedback: Settings → Help & Feedback
3. Slack: #android-testing channel
4. Email: testing@kordant.ai

Feedback Template

**Issue Title:** [Brief description]
**Device:** [Model, Android version]
**Steps to Reproduce:**
1. 
2. 
3. 
**Expected:** 
**Actual:** 
**Screenshots:** (attach if possible)
**Severity:** [Critical / High / Medium / Low]

Crash Reporting

Firebase Crashlytics is integrated and automatically reports:

• Native crashes (Java/Kotlin)
• ANRs (Application Not Responding)
• Non-fatal exceptions
• Custom logs

Monitoring Dashboard

• Firebase Crashlytics Dashboard
• Alert configured for crash-free session rate < 99%

Iteration Cycle

1. Build (Day 1): Fix critical bugs, prepare new AAB
2. Upload (Day 1): Upload to internal testing track
3. Test (Day 2-7): Testers validate, report issues
4. Triage (Day 7): Review feedback, prioritize bugs
5. Fix (Day 8-10): Address critical and high-priority issues
6. Repeat: Upload new build every 1-2 weeks

Known Issues

Track known issues in the project's issue tracker with label android-internal-testing.

Issue	Severity	Status	Notes
[Link]	Critical	Open	Description

Promotion to Closed Testing

After internal testing validation:

1. Create closed testing track in Play Console
2. Set up Google Group for external testers
3. Submit for Google review (may take 1-3 days)
4. Recruit external testers via landing page
5. Monitor crash-free rate and feedback