Maybe this information would be useful for the Spe...
# spek
e
Maybe this information would be useful for the Spek developers. @robstoll was able to reproduce the error: “Seems like spek is a using the wrong classpath and is not resolving all transitive runtimeOnly dependencies (maybe this is a bug of Android Studio)”
r
If you can send a reproducer I can help investigate more.
e
https://github.com/electrolobzik/android-flow this project contains only one test, which doesn’t run correctly with Spek Framework plugin, but works fine with gradle build in terminal
r
Thanks! I’ll have a look this coming weekend.
👍 1
e
An workaround for this is adding transitive dependencies explicitly to the build gradle:
Copy code
// assertion
    testImplementation "ch.tutteli.atrium:atrium-infix-en_GB:0.12.0"
    testImplementation "ch.tutteli.atrium:atrium-core-robstoll:0.12.0"
    testImplementation "ch.tutteli.atrium:atrium-core-robstoll-lib:0.12.0"
    testImplementation "ch.tutteli.atrium:atrium-domain-robstoll:0.12.0"
    testImplementation "ch.tutteli.atrium:atrium-domain-robstoll-lib:0.12.0"
But I suppose Spek plugin should work correctly if gradle does..
@raniejade I have also similar issue with Mockk:
java.lang.NoClassDefFoundError: io/mockk/proxy/MockKAgentFactory
and adding all Mockk transitive dependencies explicitly solved the isse.
r
Thanks! I wonder if the problem is specific to AS only - I was not able to look at it during the weekend unfortunately. I'll find some time this week.
r
I never had such issues with Spek + Atrium in Intellij. Thus I guess it is related to AS
r
That's super weird, IJ and AS plugin both share the same code.
r
@raniejade seems like the problem still exists: https://github.com/robstoll/atrium/issues/827
👀 1
👍 1