Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Cannot run individual instrumented tests
See original GitHub issueUsing gradle to try to run an individual instrumented test method will instead run all tests within that method’s class.
E.g. running ./gradlew clean connectedAndroidTest -Pandroid.testInstrumentationRunnerArguments.class=stupidSampleGradleProject.StupidConnectedTest#stupidConnectedPassTest will run all tests in the StupidConnectedTest class, rather than only the specified one. (See https://github.com/mannodermaus/android-junit5/issues/174 for the approximate build.gradle and sample test file configuration I’m using).
I verified that this was not an issue when running equivalent JUnit 4 instrumentation tests.
Let me know if you need more details to reproduce!
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Released in 1.2.0!
Thanks for confirming! I’d like to vet your other issue as well before committing to a full release, so please stay tuned for more once I get another time slot.