Troubleshoot “NO TESTS RAN” errors
On the App Automate dashboard, the Tests/Sessions field tells you the number of tests that have passed or failed. However, if your tests do not run at all, then you see the No Tests Ran error in the Tests/Sessions field. The test details section shows either of these two error messages:
Error 1: No test cases were executed
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.
-
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, andrunner_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>
Error 2: Could not start a session
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 Flutter tests, note that it is associated with BrowserStack. For assistance on this issue, reach out to us.
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
We're sorry to hear that. Please share your feedback so we can do better
Contact our Support team for immediate help while we work on improving our docs.
We're continuously improving our docs. We'd love to know what you liked
Thank you for your valuable feedback!