java.lang.AbstractMethodError about android-junit5 HOT 5 CLOSED

I can reproduce the issue here, and it's tied to the android-junit5-embedded-runtime dependency. It seems like overriding the JUnit 5 Runtime causes an incompatibility with the way Android Studio 2.x is hooking into the launch process, most likely due to renamed internal APIs.

You can see that the method doesn't even exist anymore inside IdeaTestRunner.java. I guess it would be necessary to override more of the standard JUnit runtime classes to make this work, however that might break other internals of AS (the embedded runtime is a dirty hack as it is already…).

I'm afraid that you are going to need to run your unit tests from Gradle directly (./gradlew junitPlatformTest works just fine), at least for the time being, or switch to the AS 3.x Beta. I'll extend the info in the README to explicitly state this incompatibility though.

from android-junit5.

Actually, let me keep this open & experiment a little with including more IntelliJ JARs into the embedded runtime. I'll keep you posted! Might be a few days, though.

from android-junit5.

@mannodermaus, thanks! Currently I can't migrate to AS 3 beta for this project until AS is in final version. But it will be soon as we know Android team is working hard. So, maybe just try, but don't spend so much time on it. I will stick with JUnit4 for a while.

from android-junit5.

@mannodermaus, I tried with AS 3 beta7, but the embedded-runtime library is still necessary. However, there it works.

from android-junit5.

Yes, even the latest Beta of Android Studio 3 isn't "up-to-date enough" with IntelliJ's master branch to fix the incompatibility issue present in older versions, so the embedded-runtime is required there as well. As for Android Studio 2, I haven't managed to replace the JUnitStarter responsible for accessing the removed setStreams method in the same way, so I'm afraid that launching JUnit 5 tests from the IDE directly isn't going to work with AS 2. I'll update the Readme and attach a notice there. Again, running the Gradle task directly still works, of course.

Thanks for making me aware of this!

from android-junit5.