This seems to be an issue with Android Studio inte...

# kotlintest

[LeoColman]

This seems to be an issue with Android Studio integration with JUnit... If you run via ./gradlew test do all tests run?

[dave08]

I just tried, I get 1 test completed, 1 test failed and:

.... > initializationError FAILED
    java.lang.reflect.InvocationTargetException
        Caused by: java.lang.NoClassDefFoundError at ....

But the class is in the module... 🤔

[dave08]

In the UI it just says no tests found though...

[LeoColman]

Are you using JUnit 5?

[LeoColman]

I believe that for Android you must use JUnit 4 for UI tests

[LeoColman]

It doesn't understand junit5 yet

[dave08]

I followed the instructions on Github...

[LeoColman]

I think we don't have explicit support for Android yet

[LeoColman]

And for that reason android support is not exactly documented

[dave08]

If you are using Gradle+Kotlin, this works for both Android and non-Android projects:

Kotlin (build.gradle.kts)

tasks.withType<Test> {

useJUnitPlatform()

}

dependencies {

testImplementation("io.kotlintestkotlintest runner junit53.3.0")

}

[dave08]

From the repo's readme

[LeoColman]

For testImplementation it works

[LeoColman]

It's different from androidTestImplementation

[dave08]

That's what's failing...

[LeoColman]

testImplementation is plain unit tests

[LeoColman]

You're saying that testImplementation is failing?

[LeoColman]

They're not UI tests

[dave08]

I get empty tests in Intellij (which I referred to as the UI -- to display test results), when I run them from the file tree, only when I run individual tests, it works...

[dave08]

I mean Android Studio in this case..

[dave08]

When run from the command line I got: https://kotlinlang.slack.com/archives/C18FWPKKL/p1578567080002700?thread_ts=1578502537.002600&amp;cid=C18FWPKKL

[dave08]

Could it be? Maybe because I'm using r8 and proguard to reduce the size of the debug apks, by minifying all the libs w/o the code...?

[dave08]

But the UI should really have reported that...

[LeoColman]

Ah, I see, I understood everything wrong

[LeoColman]

Hmm... If you run a single test it works in Android Studio, right?

[LeoColman]

The issue is running with more than one test

[dave08]

This is the error from Android Studio:

Internal Error occurred.
java.util.NoSuchElementException
	at java.util.ArrayList$Itr.next(ArrayList.java:862)
	at java.util.Collections$UnmodifiableCollection$1.next(Collections.java:1042)
	at com.intellij.junit5.JUnit5TestRunnerUtil.createSelector(JUnit5TestRunnerUtil.java:202)
	at com.intellij.junit5.JUnit5TestRunnerUtil.buildRequest(JUnit5TestRunnerUtil.java:82)
	at com.intellij.junit5.JUnit5IdeaTestRunner.startRunnerWithArgs(JUnit5IdeaTestRunner.java:55)
	at com.intellij.rt.execution.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:47)
	at com.intellij.rt.execution.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:242)
	at com.intellij.rt.execution.junit.JUnitStarter.main(JUnitStarter.java:70)

[dave08]

And on the left side where the test results are normally shown, it says "No tests were found"

[LeoColman]

It seems that IntelliJ is trying to execute the way it know JUnit. If you try to run in the UI, but via Gradle, do things work?

[dave08]

From the gradle side-bar, it generates an html report that gives me the same ClassNotFoundException I got on the command line, with an initialization error.

[LeoColman]

Can you get me some more of the error from that ClassNotFound?

[dave08]

Caused by: java.lang.ClassNotFoundException: net.bytebuddy.dynamic.MethodTransformer$Simple
	at <http://java.net|java.net>.URLClassLoader.findClass(URLClassLoader.java:382)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	... 29 more

[dave08]

And before that:

Caused by: java.lang.NoClassDefFoundError: net/bytebuddy/dynamic/MethodTransformer$Simple
	at org.mockito.internal.creation.bytebuddy.MockBytecodeGenerator.generateMockClass(MockBytecodeGenerator.java:38)
	at org.mockito.internal.creation.bytebuddy.CachingMockBytecodeGenerator$CachedBytecodeGenerator.generate(CachingMockBytecodeGenerator.java:72)
	at org.mockito.internal.creation.bytebuddy.CachingMockBytecodeGenerator$CachedBytecodeGenerator.getOrGenerateMockClass(CachingMockBytecodeGenerator.java:64)
	at org.mockito.internal.creation.bytebuddy.CachingMockBytecodeGenerator.get(CachingMockBytecodeGenerator.java:27)
	at org.mockito.internal.creation.bytebuddy.ByteBuddyMockMaker.createProxyClass(ByteBuddyMockMaker.java:54)
	at org.mockito.internal.creation.bytebuddy.ByteBuddyMockMaker.createMock(ByteBuddyMockMaker.java:27)
	at org.mockito.internal.util.MockUtil.createMock(MockUtil.java:32)
	at org.mockito.internal.MockitoCore.mock(MockitoCore.java:55)
	at org.mockito.Mockito.mock(Mockito.java:1449)
	at org.mockito.Mockito.mock(Mockito.java:1362)

[dave08]

But I have the Mockito dependency...

[LeoColman]

Hmmm

[LeoColman]

KotlinTest depends on Bytebuddy at some point

[LeoColman]

Perhaps they're conflicting

[LeoColman]

You can exclude Bytebuddy from KotlinTest

[dave08]

Actually, I used the newest version of KotlinTest, with an older one of Mockito (and I think also Mockk --- I don't really have the time to rewrite all those old tests...)

[dave08]

Ok, I'll try...

[dave08]

But if Mockito is older, wouldn't KotlinTest maybe count on some new features that won't exist?

[LeoColman]

I think the syntax is similar to this:

androidTestImplementation("io.kotlintest:kotlintest-runner-junit4:3.4.2") { exclude(module = "objenesis") }

[LeoColman]

But if Mockito is older, wouldn't KotlinTest maybe count on some new features that won't exist?

I don't think so. We depend on that for very specific features, such as mocking LocalDate.now()

[LeoColman]

I think the syntax is similar to this:

(This is actually a case where I had to exclude something for android, as Objenesis doesn't work with older androids)

[dave08]

Doesn't look like it ...

testImplementation("io.kotlintest:kotlintest-runner-junit5:3.4.2") {
        exclude(module = "byte-buddy")
    }

Maybe I should add the group?

[LeoColman]

Can you see in the dependency tree if Kotlintest is still using it as a dependency?

[dave08]

Nope, it's not there anymore, so the exclude worked... but I have this:

+--- org.mockito:mockito-core:1.10.19 -> 2.0.52-beta
|    +--- net.bytebuddy:byte-buddy:1.3.16 -> 1.9.3
|    \--- org.objenesis:objenesis:2.1 -> 2.6

(where Mockk is the one requiring 1.9.3), this could be my problem?

[LeoColman]

It could be possible

[LeoColman]

Anyway to update mockito to use the latest?

[LeoColman]

IDK if its latest version can use the latest bytebuddy

[dave08]

I'll try that now (hoping there weren't too many breaking changes...)

[dave08]

Seems like now on the command line my tests run, but in AS still no tests detected...

[LeoColman]

But still an exception?

[LeoColman]

Personally, I never run more than one test class through android studio, so I never faced that kind of issue

[LeoColman]

My guess is that it 'hardcodes' the JUnit execution

[dave08]

Not that one, only an NPE in certain tests...

[dave08]

So you mean just runs multiple tests from command line... 🤕

[LeoColman]

Personally, I don't run multiple tests

[LeoColman]

When developing a feature, I write tests for it

[LeoColman]

And then I go for a TDD approach
• Write some of the feature
• Write some of the tests
• Repeat

[LeoColman]

When writing the tests, I execute that single class

[dave08]

But you don't run all your tests to see if there was a regression?

[LeoColman]

When I'm done with the feature I run all the tests from the command line just to see if I didn't by accident break something else

[LeoColman]

And for that I just go ./gradlew test

[LeoColman]

I don't run all my tests every time, just when I'm ready to deliver the feature

[LeoColman]

But that's me, there's no problem with running the tests more than once

[LeoColman]

I just say that I myself don't use that feature in Android Studio, so I don't even know how it works x=

[dave08]

... which is not as easy to see what failed, AS displays it so much nicer... I had to make major changes recently and was expecting things to "blow up", reading test results from the command line is a bit of a pain...

[LeoColman]

Maybe I'm just used to it tho. I never uses that display from AS, even when I was using Java + Junit hahah

[LeoColman]

When I'm making major changes, I make a chance in a class and then run that class tests

[dave08]

At some point in time it used to work even with KotlinTest... It seems to come and go...

[LeoColman]

And do that for every class

[LeoColman]

Do it seem to come and go in the same version?

[LeoColman]

Or you think that a new version broke that execution?

[dave08]

I guess it depends on the project.

Truth is, I updated KotlinTest for running these tests, but I've had "come and go"s in the past too...

[dave08]

I think it only happens in certain situations, I don't think it's the version of KT...

[LeoColman]

I love android, but I hate android. Sometimes it can compile my code, sometimes it can't... and that's just because it doesn't want to anymore. Then restarting fixes everything

[LeoColman]

I think that the only way to fix that is to investigate JUnit's setup itself, I don't believe KotlinTest can do anything for it to work flawlessly everytime

[LeoColman]

@sam what do you think?

[LeoColman]

And by JUnit's setup I mean how Android Studio expects it to work

[LeoColman]

Perhaps improving our plugin and making this feature work better with it is a more feasible approach

[dave08]

I know you're not the only ones, a LONG time ago when I was working with Spek they had the same problems with their plugin... I don't know if they solved it...

[sam]

This is the worlds longest thread, what is it you want me to think about @LeoColman

[LeoColman]

TLDR

[LeoColman]

Android Studio "Execute all tests" doesn't work flawlessly with KotlinTest

[sam]

as part of 4.0 we're putting a big emphasis on android

[LeoColman]

But I don't think that matters. It seems that it's a problem with the tool and KotlinTest

[LeoColman]

We're putting an effort with tooling for android, and not exactly on how AndroidStudio works

[sam]

No, we're going to do both

[sam]

As part of the MPP work