Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure CompileWithTargetClassAccessExtension only uses the Jupiter TestEngine #28900

Closed
sbrannen opened this issue Aug 1, 2022 · 0 comments
Closed
Assignees
Labels
in: test Issues in the test module theme: aot An issue related to Ahead-of-time processing type: bug A general bug
Milestone

Comments

@sbrannen
Copy link
Member

sbrannen commented Aug 1, 2022

Commit 9dd7f54 addressed the issue of having the TestNG TestEngine for the JUnit Platform (JUnit 5) on the test runtime classpath by allowing org.testng types to pass through to the original ClassLoader; however, that fix merely obfuscates the underlying issue.

The underlying issue is that the CompileWithTargetClassAccessExtension is only applicable to JUnit Jupiter tests and therefore should launch the JUnit Platform with only the JUnit Jupiter TestEngine active.

@sbrannen sbrannen added in: test Issues in the test module type: bug A general bug theme: aot An issue related to Ahead-of-time processing labels Aug 1, 2022
@sbrannen sbrannen added this to the 6.0.0-M6 milestone Aug 1, 2022
@sbrannen sbrannen self-assigned this Aug 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: test Issues in the test module theme: aot An issue related to Ahead-of-time processing type: bug A general bug
Projects
None yet
Development

No branches or pull requests

1 participant