Option for adding and extra TestResultCollector when executing tests

[Jiri Vanek]

On 8/11/25 13:16, Vladimir Sitnikov wrote:
>  >Jcstress can be wrapped like this. And it may be much more secure then repalcing the internal runner, which is doing its job pretty well. Especially if you do not care  about the dynamic nature of test variants. Such test files can be
> easily provided artifact.
> 
> Could you please clarify how one can "wrap jcstress like this"?
> 
> Just to recap:
> 1) I would like ./gradlew test to work the same for both regular junit tests and jcstress tests
> 2) I would like to execute JCStress-based tests from IDE (e.g. IntelliJ IDEA) with regular "run test" action.
> 
> I don't quite get the way you suggest to wrap it.

That was refereing to possibility to generate junit test files.

I can imagine the build of jcstress generates full set of classes:   org.openjdk.jcstress.junit.whatever
where each @test method, will call `org.openjdk.jcstress.Main("org.openjdk.jcstress.tests.whatever");`

That maybe to dummy for your usecase, but I'm still unsure why you need it at all (and is  much safer then replacing the current runner).

j.