Only one test method in my snippet but add two more if you need to

hmm thats not at all what i want

This snippet is equivalent to the ScalaTest example you gave

What's not right with it?

in your example if i added 2 more test methods it would run 30 tests.

i want my 3 tests to run, and each one with a separate server instance (for isolation)

Then create a different instance for each server

Or pass multiple servers in the constructor and have each method use their own

plenty of ways to design that

if that test grows to 40 methods or so that will be really painfiul

Then create a function that instantiates new server as needed and have these methods call that

Seriously, I'm not sure what's blocking you here

look

each test method could just start with server=DockerUtils.getServer. and end with server.stop

maybe in a finally block

and i want that code in a beforeEach/afterEach

because its good practive

and that would work best if each test had a fresh instance of the test class like in junit because then i could just use an instance variable

In Kotlin, I'd just go ahead and use `use`:

@Test fun test() {
  createServer().use {
    // test
  }
  // server gets automatically stopped
}

ok, still you would have that same code in each one of your tests

i guess my point is that beforeMethod would be more useful if it had a scope that it shares with the test method

which is probably the reason why junit creates a fresh instance of the test class for each test method

Hi, @christophsturm: I see this line in sample of your code, what is

lazy

there? annotation?

lazy val server = DockerServerUtils.runningServer()

@igor.korotenko: its scala code. thats a modifier that indicates that the value should be computed lazily

@christophsturm: hmm, looks nice, would like to have this in kotlin, look more concise that

val x by  lazy {}

Maybe this is relevant for some of the test framework/library developers. @natpryce (HamKrest), @hhariri (Spek), @raniejade (KSpec), @sam (kotlintest) The JUnit 5 team wants to provide a minimal common foundation for JVM testing libraries. Both opentest4j and junit5 are close to a first milestone release (I guess). https://github.com/ota4j-team/opentest4j#projects-already-contacted

Yeah, opentest4j currently only provides common exceptions. I opened up a discussion regarding

junit-engine-api

and

junit-launcher

https://github.com/ota4j-team/opentest4j/issues/11, maybe you guys can share your thoughts.

I'm having some problems getting Spek set up, I wonder if someone can help with some rubber-duck debugging 🙂

I've add the dependency to my build.grade:

testCompile(group: 'org.jetbrains.spek', name: 'spek', version: '1.0.9', ext: 'pom')

and I have the repo:

repositories {
    mavenCentral()
    maven {
        url "<http://repository.jetbrains.com/all>"
    }
}