Custom test tasks are harder to write with 2.10.x

[jansorg]

Describe the need of your request

AFAIK 2.10.x changed custom test tasks in a way that the plugin configuration is not reused from the main project.
Projects with a complex plugin dependency setup and custom test tasks are much harder to maintain now because both the project and the custom test task need a (duplicated) setup of plugins, bundled plugins, etc.

Proposed solution

A flag to tell the test task to reuse the main plugin setup or a method/mechanism to copy the plugin setup from the project's base setup to the custom test task would be very helpful.

Alternatives you've considered

No response

Additional context

Furthermore, custom tests provide the plugin dependency methods via IntelliJPlatformPluginsExtension and the regular plugin dependencies are added via ``IntelliJPlatformDependenciesExtension`. This complicates and prevents reuse, e.g. with an extension method in the Gradle build file.

[tristanshang]

@jansorg, I am not sure whether I met the same issue as you .
what I met is that the custom test action can not get the classpath of test ask automatically. from 2.6.
for example. below custom action will get ClassNotFoundException in some situation(intellij depedencies)

task unitTest(type: Test, description: 'Runs the unit tests.', group: 'Verification') {
useJUnit {
includeCategories 'com.sap.category.AssistantUnitTest'
}
}
add the classpath += tasks.test.classpath is a workround for this issue. but I am not sure if it is the right way. Is there a official way to solved this issue?

this is my report for this issue but no response.
#2074