I have a plain old little java library with about ...

# testing

[Colton Idle]

I have a plain old little java library with about 20 unit tests, but now I want to just change one variable for the tests so that I have 40 tests (its the same 20 tests, ran twice, with different inputs). How can you do that with kotlin + gradle?

[andylamax]

writing here so that I get notifications on how to solve this as well

[Mykola Gurov]

Depends on what kinda of these inputs is that - depending ono that you might want different approaches

[Mykola Gurov]

Also depends on how are you going to run all those tests, do they have to run all together with maven/gradle in the same test suite, or can they be invoked separately

[Mykola Gurov]

One hacky way would be to use system properties to parameterize tests.

[Mykola Gurov]

Another option is to refactor the tests into Dynamic tests with @TestFactory of Junit5 (I assume, the unit tests are written in Junit?) . @ParameterizedTest is also an option, although I personally find it very inconvenient.

[Mykola Gurov]

In case those 20 tests are in the same class - junit style again - you could make a subclass of that for the alternative parameter. A bit ugly, especially in regards of executing an individual test method from IDE, but sort-of works

[Colton Idle]

So I eneded up using parameterized tests in kotlin + junit4. It wasn't too bad to setup, although a little confusing. BUT I had some issues getting those parameters in @BeforeClass.

What I eneded up doing was passing params through cmd line.

Like ./gradlew :blah:tests --tests "com.mytests" -Dmyarg=FOO

[Colton Idle]

and I basically on CI just run that script twice. each time with diff args. works exactly as i need it. and i learned about parameterized tests which is cool