Skip to content

Allow alternatives to ForkingTestClassProcessor #32666

@dubinsky

Description

@dubinsky

Expected Behavior

DefaultTestExecuter hard-codes the use of ForkingTestClassProcessor. Suggested feature is an extension point that provides a way to use alternative TestClassProcessor.

Current Behavior (optional)

DefaultTestExecuter hard-codes the use of ForkingTestClassProcessor.

Context

When running tests on Scala.js, forking is not an option, so Gradle Scala.js plugin needs to use a TestClassProcessor that does not fork.

Without an extension point, the only way to make this work is to fork DefaultTestExecuter class and track changes to its Gradle original in a different repository just to be able to override one method - which is sub-optimal ;)

Proposed extension point would make it possible for the Gradle Scala.js plugin to be cleaner.

Metadata

Metadata

Assignees

No one assigned

    Labels

    a:featureA new functionalityclosed:not-fixedIndicates the issue was not fixed and is not planned to bein:testing

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions