Testing Strategy — Android Port

Testing Levels

graph TD
    L1["Level 1: Build Verification"] --> L2["Level 2: Emulator Smoke Test"]
    L2 --> L3["Level 3: Functional Testing"]
    L3 --> L4["Level 4: Device Testing"]
    L4 --> L5["Level 5: Integration Testing"]

Level 1: Build Verification

When: Every code change Where: Developer machine + CI Time: < 2 minutes

Commands

# Verify desktop build still works
dotnet build XBVault -c Release

# Verify Android build
dotnet build XBVault.Android -f net10.0-android36.0 -c Debug

# Run existing tests
dotnet test tests/XBVault.Tests -c Release

Checklist

• Desktop build succeeds with no new warnings
• Android build succeeds with no errors
• Existing unit tests pass
• No new analyzer warnings

Level 2: Emulator Smoke Test

When: After Phase 0 and Phase 1 Where: Android emulator Time: 5 minutes

Emulator Setup

1. Install Android SDK via Visual Studio or sdkmanager
2. Create AVD: Pixel 6 API 34 (Android 14)
3. Enable hardware acceleration (HAXM or Hyper-V)

Smoke Test Script

# Build and deploy to emulator
dotnet build XBVault.Android -f net10.0-android36.0 -c Debug
dotnet android:run -f net10.0-android36.0

# Or use adb
adb install -r XBVault.Android/bin/Debug/net10.0-android36.0/com.companyname.xbvault.apk
adb shell am start -n com.companyname.xbvault/.MainActivity

Checklist

• App launches without crash
• Avalonia UI renders (not blank screen)
• Bottom tab bar visible (Phase 1+)
• Tab switching works
• No ANR (Application Not Responding) dialogs

Level 3: Functional Testing

When: After Phase 2+ Where: Android emulator or device on same network as Xbox Time: 15–30 minutes per session

Test Scenarios

Connection

Browse

Installed

File Explorer

Settings

Level 4: Device Testing

When: After Phase 3 Where: Physical Android device Time: 1–2 hours

Device Requirements

• Android 8.0+ (API 26+) for broad compatibility
• Same WiFi network as Xbox Dev Mode console
• USB debugging enabled for deploy

Device-Specific Tests

Performance Tests

Level 5: Integration Testing

When: After Phase 4 Where: Device + Xbox Dev Mode console Time: 1–2 hours

End-to-End Flows

Automated Testing

Unit Tests (existing)

The existing tests/XBVault.Tests project runs on desktop. For Android:

• ViewModels are testable on any platform (no UI dependencies)
• Services can be tested with mocked HTTP/SSH
• Run existing tests as part of Android CI

UI Tests (future)

Avalonia supports UI testing via:

• HeadlessRunner for automated AXAML tests
• Custom test harness for ViewModels

Not recommended for initial port — manual testing is sufficient for Phase 0–3.

Test Environment Setup

Prerequisites

# Install Android SDK (via Visual Studio or manual)
# Required: Platform API 34, Build Tools 34.0.0

# Verify SDK
dotnet workload list  # Should show android workload
adb --version

# Create emulator AVD
avdmanager create avd -n Pixel6_API34 -k "system-images;android-34;google_apis;x86_64"
emulator -avd Pixel6_API34

Network Setup

For testing Xbox connection from emulator:

• Xbox and development machine on same subnet
• Xbox Dev Mode enabled and portal running
• Emulator uses host network (default for Android emulator)

For testing from physical device:

• Device and Xbox on same WiFi
• Use Xbox IP address (not localhost)

Bug Reporting

When issues are found during testing:

1. Capture logs:

   adb logcat -s "XBVault" > android_logs.txt
   

2. Capture screenshot:

   adb shell screencap -p /sdcard/screenshot.png
   adb pull /sdcard/screenshot.png
   

3. Include in report:
   • Device model and Android version
   • Steps to reproduce
   • Expected vs actual behavior
   • Log file and screenshot