running-instrumented-tests-via-adb

Run Android instrumented tests via adb by executing `am instrument` with `-w` and `-r` flags, bypassing Gradle entirely while producing deterministic stdout framing for reliable CI consumption.

The adb shell exit code is misleading for instrumented tests. You must parse the `INSTRUMENTATION_STATUS_CODE` values from the raw output, where `-2` indicates failure and `-1` indicates an error, to accurately detect pass/fail outcomes.

To run a single test method, use the `-e` argument to specify the target, such as `-e class com.example.MyTest#myMethod`, followed by your test package and runner component name in the `am instrument` command.

Yes, you can use AndroidX Test Orchestrator by passing it as the positional last argument, wiring the runner with `-e targetInstrumentation`, and optionally enabling `clearPackageData` for test isolation.

You can shard instrumented test suites by passing `-e` arguments with `numShards` and `shardIndex` to `am instrument`, allowing you to slice and distribute test runs across multiple CI executors.