Overview
The newly introduced TestRuntimeHintsRegistrar API allows one to register hints specific to a given test class; however, there are scenarios in which the logic involved in determining what might need run-time hints resides in a TestExecutionListener.
For example, the SqlScriptsTestExecutionListener contains private logic for determining default SQL scripts, and that logic should not be duplicated outside the SqlScriptsTestExecutionListener.
In light of that, we should introduce an AotTestExecutionListener API that extends TestExecutionListener and allows a TestExecutionListener to opt in for AOT processing support, analogous to what the AotContextLoader API does for a SmartContextLoader.
Related Issues
Overview
The newly introduced
TestRuntimeHintsRegistrarAPI allows one to register hints specific to a given test class; however, there are scenarios in which the logic involved in determining what might need run-time hints resides in aTestExecutionListener.For example, the
SqlScriptsTestExecutionListenercontains private logic for determining default SQL scripts, and that logic should not be duplicated outside theSqlScriptsTestExecutionListener.In light of that, we should introduce an
AotTestExecutionListenerAPI that extendsTestExecutionListenerand allows aTestExecutionListenerto opt in for AOT processing support, analogous to what theAotContextLoaderAPI does for aSmartContextLoader.Related Issues