The runtimeClasspath of the configured testSourceSets is added to the additionalClasspath, but it might also be needed in the launch classpath.
I played with pitest-descartes and there I got some missing classes.
I have a MutationInterceptor that filters out identical mutations.
It uses Mutant#getBytes() to find duplicates.
During this call with pitest descartes as mutation engine, I got the ClassNotFoundException unless I manually added the test runtime classpath to the launch classpath.
Maybe it would make sense to add it to both by default, not only the minion classpath.
The
runtimeClasspathof the configuredtestSourceSetsis added to theadditionalClasspath, but it might also be needed in the launch classpath. I played withpitest-descartesand there I got some missing classes. I have aMutationInterceptorthat filters out identical mutations. It usesMutant#getBytes()to find duplicates. During this call with pitest descartes as mutation engine, I got theClassNotFoundExceptionunless I manually added the test runtime classpath to the launch classpath. Maybe it would make sense to add it to both by default, not only the minion classpath.