not yet, but if afaik if you run tests on jvm it’ll use

javac

to compile them

The upgrade to JUnit 5 is going to be a bit problematic with android users.

They heavily rely on java 8 features

it will be problematic only for instrumentation tests that run on Android emulator/device where not all Java 8 features will be available

but for tests that run on computer (unit, integration) it won’t be a problem

true, but they definitely need jdk 8

most of Android developers use jdk8, and most of them don’t write instrumentation tests unfortunately

@raniejade: can you give an example of java8 features that Spek based on JUnit5 will need?

JUnit5 uses streams heavily

default methods as well

those will be available on Android N+ https://developer.android.com/preview/j8-jack.html

and again, it’ll only affect instrumentation tests which unfortunately not a lot of developers write

What does JUnit bring to Spek exactly? Wouldn't you be better off just implementing your own mini engine to run test methods?

Reporting, IDE support and so on

i think that making everything junit compatible is one of the biggest problems of unit testing in java. scalatest started from scratch and thats why its so good

I understand it's useful in the early stages to focus on the main features but yes, as time goes by, going independent is important

well, probably. but for now when you write Spek tests you don’t see any JUnit specific things. IDE, build tools, CI reporting and other integrations will consume a lot of time for maintainers if they go independent

spek-api

and the junit5 stuff are completely decoupled. Moving forward, going independent is best. Opens up a lot of possibilities.

sounds good. are there any plans to run tests multi threaded?

@christophsturm: for now you can do it via build tools, Gradle allow that for instance

Don’t tie it to build tools, bite the bullet, the framework should support that natively.

yeah, i run the tests in idea most of the time. right now we are using testng because thats the only framework that supports it 🙂

ok, just in case if you use Mockito — don’t run tests in parallel on one JVM, it’ll break Mockito

really? i thought that was fixed

Is Mockito thread-safe? For healthy scenarios Mockito plays nicely with threads. For instance, you can run tests in parallel to speed up the build. Also, you can let multiple threads call methods on a shared mock to test in concurrent conditions. Check out a timeout() feature for testing concurrency.

i have this bet running with myself, that if i get my testsuite to scale to 8 cores I’m going to buy a macpro

also running tests multithreaded in gradle spins up separate vms. I’m trying to speed up super fast test suites. (make it run in 5 seconds instead of 40)

What’s the best way to declare a sut or dependency in spek? Right now I have:

var instance = ActivityInstance(title = "Calculator", handle = "12345", persistentId = "123")
beforeEach { instance = ActivityInstance(title = "Calculator", handle = "12345", persistentId = "123") }

Since

ActivityInstance

has no default ctor, I have to init it twice?

@jasper: another way is to make instance nullable

ActivityInstance?

, but you have to use

!!

whenever you reference it.