Troubleshoot “NO TESTS RAN” errors

Here is the complete error:

No test cases were executed. Please refer to our troubleshooting guide to debug further. You can also check the output of the dry run logs/instrumentation logs here.

• If you encounter the above error, it may be due to an incorrect usage of the filtering parameters in your REST API request. The filtering logic might have resulted in 0 tests and hence no tests could be executed. Please verify the filtering logic and if you have used the correct filtering parameters.

• When auto shards strategy is enabled for an Espresso test suite, due to the default behavior of AndroidJUnitRunner, some shards might not get a test assigned. Please use lesser shards for this group of tests or choose a different sharding strategy.

• The uploaded test suite has 0 test cases and hence no tests could be executed.

• If the error is not caused by the above-mentioned reasons, then please run the command below in your terminal by replacing the values with your class_name, test_package, and runner_class. The output helps you find the cause of the error:

adb shell am instrument -w -r -e class <class_name> -e log true <test_package>/<runner_class>

Here is the complete error:

Could not start a session: Something went wrong. Please try to run the test again.

If you encounter the above error while running your Espresso tests, note that it is associated with BrowserStack. For assistance on this issue, reach out to us.