cedric suggested using factories but i didnt really understand how that relates to my use case. also running it inside of idea is a must for us

I also suggested that you can reset the state of your object in a

@BeforeClass

in TestNG, which gives you the same thing as creating a new instance every time. Or you can clear that state in

@AfterClass

Otherwise, I think spek should support multithreaded tests

@cedric but beforeClass runs only once per class, and not once per test. also i don’t want to reset it, i want multiple tests running concurrently and each have their own class instance variables

Right sorry meant

@BeforeMethod

this is how i do it now in scalatest: https://kotlinlang.slack.com/files/christophsturm/F18KRS5JQ/-.kt

Untitled.scala

so i have 10 tests, they run in parallel, and each one has a fresh instance of the app running in a docker container

after

runs after each test method I assume?

yes, in this case it does

How is that different from

@AfterMethod

?

its not different, but this test would not work if i had just one instance shared between all tests

because lazy val server is different for each test

Ok so yes, in this case,

@Factory

is the answer and it lets you manage the instances of your test classes yourself.

i thought that factory is for dynamically creating test classes?

so i have a testng test and 10 methods annotated with @Test. how do i give them each a fresh instance?

From the doc:

public class WebTestFactory {
  @Factory
  public Object[] createInstances() {
   Object[] result = new Object[10]; 
   for (int i = 0; i < 10; i++) {
      result[i] = new WebTest(i * 10);
    }
    return result;
  }
}

ok but isnt that for running the same test multiple times with different parameters?

Up to you really, you're welcome to return whatever test instances you want from the factory method

Sometimes it will be the same class with different constructor parameters, other times totally different instances

ok but then i need every test in a separate clas

No, you could pass the server in the constructor

and create a different server in the loop above

sure, but i want 10 totally different test that have nothing to do with each other. they just all need a server instance

to run isolated from each other

I don't know what else to tell you, how is the snippet above not solving your problem?

i updated my snippet to contain 3 tests. how would i do that with a factory?

i must be missing something obvious here

Roughly:

class HttpEndpointIT(val server: DockerServer) {
    @Test
    fun test() { }
    
    @AfterMethod
    fun after() = DockerUtils.stop(server)
}

class TestFactory {
    @Factory
    fun create() = (1..10).map { HttpEndpointIT(DockerServer(it)).toArray()
}

then i have one test class with 3 tests, and it runs 10 times