You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a new unit testing / integration testing plugin(s) from ground up to use JUnit Jupiter plattform instead of handling all requirements on our own (as surefire/failsafe does). This includes selection of the test classes / test files etc. via the platform.
The usage of the JUnit Jupiter Platform make the support for future testing frameworks easier, because it's foundation is based on the JUnit Jupiter platform.
Supporting other testing frameworks is already offered via the JUnit Jupiter Platform (or via junit-jupiter-vintage, other engines):
In consequence the whole configuration(parallelizing, selecting files, suites etc.) for running unit- and integration tests will be done via the JUnit Jupiter platform... That means we would have in the end a single way of configuration instead of several ways.
TODO's
Analyse what exactly has to be done to support classpath/module path
Goal
Create a new unit testing / integration testing plugin(s) from ground up to use JUnit Jupiter plattform instead of handling all requirements on our own (as surefire/failsafe does). This includes selection of the test classes / test files etc. via the platform.
Requirements
A requirement is to support the JPMS module system for testing incl. integration testing. This might be related to Better Java Module System support for Maven 4 #11
The usage of the JUnit Jupiter Platform make the support for future testing frameworks easier, because it's foundation is based on the JUnit Jupiter platform.
Supporting other testing frameworks is already offered via the JUnit Jupiter Platform (or via junit-jupiter-vintage, other engines):
In consequence the whole configuration(parallelizing, selecting files, suites etc.) for running unit- and integration tests will be done via the JUnit Jupiter platform... That means we would have in the end a single way of configuration instead of several ways.
TODO's
Based on #32
The text was updated successfully, but these errors were encountered: