Skip to content

Conversation

@souvlakias
Copy link
Contributor

Addresses #6457

The initial thought was to have users use the .testOnly task and pass globSelectors, but that would require for us to discover all of the test packages,classes and functions.

Until we explore how to do that correctly, we could just pass any additional args the user provides to the test task to adb, for manual adb configuration
Example usage:

> ./mill app.androidTest -e class <className1>,<className2> -e package <pkgName1>,... # etc

TODO: document this somewhere

@vaslabs
Copy link
Contributor

vaslabs commented Jan 8, 2026

imo we should have an androidTest dedicated example to demonstrate the usage of this. just a simple app with a few android test classes that run fake assertions and demonstrate both failures and successes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants