Ensure CompileWithTargetClassAccessExtension only uses the Jupiter TestEngine #28900
Labels
in: test
Issues in the test module
theme: aot
An issue related to Ahead-of-time processing
type: bug
A general bug
Milestone
Commit 9dd7f54 addressed the issue of having the TestNG
TestEngine
for the JUnit Platform (JUnit 5) on the test runtime classpath by allowingorg.testng
types to pass through to the originalClassLoader
; 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 JupiterTestEngine
active.The text was updated successfully, but these errors were encountered: