Create FixtureResolver

[veluxer62]

The FixtureResolver functions to generate function parameter data for test.

I referred here:

• https://junit.org/junit5/docs/current/user-guide/#extensions-registration
• https://github.com/junit-team/junit5-samples/blob/master/junit5-jupiter-extensions/src/main/java/com/example/random/RandomParametersExtension.java

[veluxer62]

When I add Map and List type parameter, There are empty value in the test parameter data. Is there any problems in my code?

[TWiStErRob]

I had similar problems when I wrote a Kotlin extension function. I had to use fixture.collections() to create them. Not sure why though.

[veluxer62]

@TWiStErRob When worte Map and List type variable in class. fixture generated data as I expected. See 22 to 31 lines in FixtureResolverTest.java .

[TWiStErRob]

Yeah, the difference is having it as part of another Class (field, ctor param); that works fine, but directly fixture.create(new SpecimenType<List<String>>() {}) doesn't work.

[rses]

I've had the same issue with collections - ended up using Kotlin generator functions, didn't look much into it and chalked it up to type erasure.

While this is a good added feature (parameterised @Fixture), I'm just wondering why not just use member variables with @Fixture? Is it for readability? (genuinely asking, not being a troll :) )

[TWiStErRob]

@rses it's just how JUnit 5 works. In most test classes individual tests don't use all of the fixtures, and also they also create more in local variables. There's a reason while injected parameters become a thing in JUnit 5.

Do you mean operator invoke by "generator"?