https://bz.apache.org/bugzilla/show_bug.cgi?id=69684
Bug ID: 69684
Summary: junitlauncher sends individual discovery requests per
class to JUnit platform
Product: Ant
Version: 1.10.15
Hardware: All
OS: All
Status: NEW
Severity: major
Priority: P2
Component: Optional Tasks
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
The current implementation of junitlauncher sends one discovery request per
test class that should be executed.
Is this intended?
Because I see various drawbacks in this approach, instead of sending one
discovery request for all tests to be executed.
- It is much slower as the engine has to do a full discovery each time
- It breaks some test execution listeners, for example if you use the JUnit
built-in
`org.junit.platform.reporting.legacy.xml.LegacyXmlReportGeneratingListener`,
then you only get one JUnit XML file with the tests of one test class, as the
reports are overwritten, due to that listener constructing the file path from
the top-most test descriptor which is the engine name
- Probably most important, it breaks parallel test execution also making things
much slower. With the current tactic only tests within one class can run in
parallel, but tests from different classes can not be run in parallel, as each
class is run separately and so they cannot use the parallel running support
properly that some JUnit Platform Engines like Jupiter or Spock provide
- ...
--
You are receiving this mail because:
You are the assignee for the bug.
