Issue
I have a scaled project that has at least 12 modules. I would like to start the app module and run the project. Every time I try to start it, I keep getting the message that
$ adb shell CLASSPATH=$(pm path androidx.test.services) app_process / androidx.test.services.shellexecutor.ShellMain am instrument -r -w -e targetInstrumentation *** ... *** androidx.test.orchestrator/androidx.test.orchestrator.AndroidTestOrchestrator
Client not ready yet..
Started running tests
Test running failed: No test results.
I read through the AndroidX documentation of espresso usage and have
- included the ANDROIDX_TEST_ORCHESTRATOR
- have included the required libraries using the useLibrary function
- set up the test runner to use androidx-testRunner.
I was able to generate the tests using the Espresso test runner but every time I try to run it, I get this message. Just to be sure I made a sample app and tested the whole thing out and I am able to make instrumentation tests on the sample app.
Does anyone know what could happen in a multi-module project that uses dependency injection?
Solution
It had nothing to do with modules or project size, removing the ANDROIDX_TEST_ORCHESTRATOR made it work.
Answered By - Dinesh
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.