you can still do this:

assertBucketWasAddedInList(testListSubscriber)

yeap, but it doesn’t resolve my issue

I think I’ll use the class loader, and wrap in a simple function.

@nhaarman: you’re creator of mokito-kotlin, maybe you could help me with PowerMock, and how to connect

Spek

and

PowerMock

, especially for mocking static methods.

I have never used PowerMock really, and there is an open issue where PowerMock doesn't play nicely with Mockito-Kotlin yet.

yep( so, is there any other way to mock static method?

dmitriy.m: jmockit can do it too

Doest it work with spek?

@christophsturm:

i havent tried it with kotlin. but i remember that its the only other mocking lib apart from powermock that can mock static methods

what you really should do instead is make the method not static 🙂

))) it's a black box) it can do it right now)

who has used

Spek

with

PowerMock

? how to connect one with another?

Haven’t tried, but

PowerMock

supports delegation to other runners, so you can try to run tests with

PowerMockRunner

and delegate execution to

JUnitSpekRunner

https://www.jayway.com/2014/11/29/using-another-junit-runner-with-powermock/

@dmitriy.m: and usual advice: avoid

PowerMock

, it’s a sign of bad design if you need it 🙂

all static methods and final classes are bad design?

no, only those which require you to mock them in order to test your software

ok, i see. thanks you guys!

Any support in Spek for assertions of future values? Eg Kiwi (iOS library):

[[expectFutureValue(receivedContext) shouldEventuallyBeforeTimingOutAfter(5.0)] beNonNil];

<— Very wordy Objective-C I tried my own

waitFor (condition) { //do something}

but got:

Method getMainLooper in android.os.Looper not mocked. See <http://g.co/androidstudio/not-mocked> for details.

ah, looks like I can use an AndroidTest instead of JUnit (ahem, n00b here)

@jasper:

Method getMainLooper in android.os.Looper not mocked.

means that you’re trying to use class (in particular

Looper

) from Android SDK during jvm tests, Android Gradle Plugin creates

mocked

jar of Android SDK classes without implementation. It’s not related to Spek and there are several solutions: * Don’t touch Android SDK classes in jvm tests * Use Robolectric * Write test as instrumentation test to run it on device/emulator instead of jvm

Yes, thank you Artem. I went for the latter approach.

Usually the problem with running tests on emulator/device is CI infrastructure and that you need to wait for

apk

and connect device/emulator during local development. JVM tests run in seconds, instrumentation takes

* x times

longer

@repa40x has left the channel

Just a heads up, I'll be merging the junit5 branch to master. We are still working out the snapshot and release build.

@michele has left the channel

We have snapshot builds now available at https://jetbrains.jfrog.io/jetbrains/spek-snapshots/. This already includes the junit5 work.

regarding the current master (just cloned 30min ago), in order to be able to run the spek-example test cases, I need to add

@RunWith(JUnitPlatform::class)

on each of the Test case (and

testCompile 'org.junit.platform:junit-platform-runner:+'

in build.gradle of that module)

otherwise putting the cursor on src/test/kotlin and Ctrl+Shift+F10 doesn't run it