Skip to content
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

Closed
olga999999 opened this issue Jun 10, 2024 · 7 comments · Fixed by #341
Closed

Test filtering doesn't work on the latest SNAPSHOT #339

olga999999 opened this issue Jun 10, 2024 · 7 comments · Fixed by #341
Assignees
Labels

Comments

@olga999999
Copy link

olga999999 commented Jun 10, 2024

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

@mannodermaus mannodermaus self-assigned this Jun 14, 2024
@mannodermaus
Copy link
Owner

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.

@mannodermaus
Copy link
Owner

This is merged into the snapshot and should be ready in about 15 minutes. Let me know if it resolves your issue!

@olga999999
Copy link
Author

Hi
Thank you for the prompt fix, but I'm still observing this issue with parametrized tests 🤔
Your screenshot shows only repeated tests, so I wonder if you've tried parametrized test and it worked?

@mannodermaus
Copy link
Owner

mannodermaus commented Jun 15, 2024

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. 🤔

Screenshot 2024-06-15 at 23 11 40

@olga999999
Copy link
Author

Hmm, I cleared gradle cache and re-synced deps, but still the same.
Actually, it seems it's still downloading the build from May 22
Download https://oss.sonatype.org/content/repositories/snapshots/de/mannodermaus/junit5/android-test-runner/1.5.0-SNAPSHOT/android-test-runner-1.5.0-20240522.143334-9.aar, took 560 ms.
And it seems there are no newer ones available on the server: https://oss.sonatype.org/content/repositories/snapshots/de/mannodermaus/junit5/android-test-runner/1.5.0-SNAPSHOT/

@mannodermaus
Copy link
Owner

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.

@olga999999
Copy link
Author

All good now, thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants