feat(qa): Android instrumented test discovery (managed devices + connectedAndroidTest)

[OBenner]

Summary

First slice (A1) of the Device & GUI Verification Roadmap: lift Android projects from L1 (JVM unit tests) to L2 (instrumented tests on an emulator).

TestDiscovery now emits an android_instrumented (type e2e) entry for Android Gradle projects:

Case	Command
Gradle Managed Virtual Devices configured	./gradlew <device>DebugAndroidTest — Gradle provisions and tears down the emulator itself, no lifecycle code on our side
src/androidTest sources, no managed devices	./gradlew connectedAndroidTest — requires an attached device/emulator
Android project without instrumented tests	no entry

Device names are parsed from both DSLs: Kotlin create("pixel2api30") and Groovy named blocks (pixel6api33 { ... }), root and app/ module build files. The unit-test gradle test command stays primary — instrumented runs are additional, mirroring the playwright/cypress pattern.

Allowlist: emulator, avdmanager, sdkmanager added to the android framework commands (joining gradlew/adb from #395).

Testing

tests/test_discovery.py: 78 passed (6 new: both DSLs, connected fallback, negative cases for missing tests and non-Android Gradle, primary-command precedence). Ruff check + format clean.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@OBenner, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5ac4e4aa-836d-442b-a942-29a5a3a385cb

📥 Commits

Reviewing files that changed from the base of the PR and between 4ea224f and b59f191.

📒 Files selected for processing (3)

• apps/backend/analysis/test_discovery.py
• apps/backend/project/command_registry/frameworks.py
• tests/test_discovery.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/android-instrumented-test-discovery

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud