Android Studio Espresso Testing Error: Empty Test Suite

by

While the question is already answered, figured it was worth posting for future visitors.

Make sure you check the logcat logs to ensure something isn’t causing issues (crash) before the test is even run. I had bad code in my @BeforeClass block which resulted in the “Empty Test Suite” message in Android Studio despite having properly set the test runner.

More Related Contents:

  1. Espresso: Thread.sleep( )
  2. Thread.sleep( ) with Espresso
  3. Testing background color espresso Android
  4. How to emulate GPS location in the Android Emulator?
  5. Making the Android emulator run faster
  6. Checking toast message in android espresso
  7. Espresso – How can I check if an activity is launched after performing a certain action?
  8. Conflict with dependency ‘com.android.support:support-annotations’. Resolved versions for app (23.1.0) and test app (23.0.1) differ
  9. In Espresso, how to avoid AmbiguousViewMatcherException when multiple views match
  10. java.lang.IllegalAccessError: Class ref in pre-verified class resolved to unexpected implementation getting while running test project?
  11. Android Marshmallow: Test permissions with Espresso?
  12. Android test code coverage with JaCoCo Gradle plugin
  13. ProgressBars and Espresso
  14. Stopping an Android app from console
  15. Android AsyncTask testing with Android Test Framework
  16. Get context of test project in Android junit test case
  17. How to generate zoom/pinch gesture for testing for Android
  18. Android RxJava 2 JUnit test – getMainLooper in android.os.Looper not mocked RuntimeException
  19. How to click on an item inside a RecyclerView in Espresso
  20. Using Espresso to Unit Test Google Maps
  21. Using Espresso to click view inside RecyclerView item
  22. How to mock method e in Log
  23. Difference between Android Instrumentation test and Unit test in Android Studio?
  24. Android unit test not mocked
  25. AndroidManifest in androidTest directory being ignored
  26. FragmentActivity can not be tested via ActivityInstrumentationTestCase2
  27. com.android.builder.testing.ConnectedDevice > hasTests[test(AVD) – 5.0] FAILED
  28. Android: Simulate WiFi in the emulator?
  29. Error java.lang.RuntimeException: Stub! in Android with Fitnesse testing
  30. Android :java.lang.SecurityException: Injecting to another application requires INJECT_EVENTS permission

Leave a Comment