Mihály Verhás

> As mentioned in my comment above `InvocationInterceptor` might not work for the `@AfterEach` case. In case that is not possible, do you want me to use `InvocationInterceptor` nonetheless even...

LGTM

Feel free to discuss it here, on Discord, on Twitter, via smoke signals, over telegram or carrier pigeon (or any other way). We'd love to hear from you! Personally, I'd...

Jimfs is not in a module and does not define a module name in the manifest. Automatic modules are not supported by gradle. Not sure how to proceed.

[935be84](https://github.com/junit-pioneer/junit-pioneer/pull/491/commits/935be844ad3339f859231fd7cc5976c1bf78cc21) is just a mistake, please revert/remove if you can.

Hey @jbduncan sorry for pushing so much stuff on your branch, I'm just trying to make it work with our modular setup because I felt it would be unfair to...

I don't see the use-case for this. You should always control your input to your tests which means no randomizing.

> I'm wondering though, why there exists such a limitation? I think it would be nicer if one could use JUnit's standard param annotations instead of the the practically similar...

My above comment is also what I consider a major challenge when trying to implement `@CartesianCsvSource` - determining which `ArgumentsProvider` should be invoked for the different arguments. E.g. this should...

After #487, we need to think of a new approach to this extension. Perhaps if `@CartesianCsvSource` provided values to all parameters? Personally, I think instead of this: ```java @CartesianProductTest @CartesianValueSource(ints...