-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test filtering doesn't work on the latest SNAPSHOT #339
Comments
Hey, thanks for reporting. I can confirm that this is indeed happening because of the change in #335, and it's no wonder it fails for a test class with test cases foreign to the JUnit 4-based Android instrumentation. Not sure yet how I want to tackle this, since there are a lot of benefits to relying on the counting performed by Android, but we definitely need to take dynamic tests into account here. |
This is merged into the snapshot and should be ready in about 15 minutes. Let me know if it resolves your issue! |
Hi |
I did and it did, yeah. The mechanism for any non-@test method is the same, so it shouldn't matter which one is used. Could be that your snapshot isn't refreshed to the latest variant from earlier today or something? Let me give this one more spin. Edit: Yes, indeed this is working as expected both from the IDE and command line. 🤔 |
Hmm, I cleared gradle cache and re-synced deps, but still the same. |
Sorry about that. Turns out Maven Central migrated off of the old authentication mechanism for publishing artifacts, and triggered the switch for this repository somewhere in the last few days. I was able to update and re-deploy, please try again. |
All good now, thanks a lot! |
Execution of the individual test cases from command line and AS doesn't work on the latest 1.5.0-SNAPSHOT. No tests are being executed at all.
It worked fine before, so most likely it is caused by #335 or #336.
Sample command:
./gradlew -Pandroid.testInstrumentationRunnerArguments.class=com.example.ExampleTest1#parametrizedTest :app:cAT
The text was updated successfully, but these errors were encountered: