Tibor17 opened a new pull request, #616: URL: https://github.com/apache/maven-surefire/pull/616
@slawekjaranowski This is a work in progress. The test reporters must not determine the test status upon timings of test events. The test reporters must not identify the test run upon text literals (e.g. class and method) of the test entry. These are all the causes why parallel tests are chaotic in JUnit5 report. These are the causes why JUnit5 and JUnit4 parameterized tests give different reports. These are the causes why Cucumber is not able to work with dynamic tests. Nevertheless this would fix the issue with memory consumption in JUnit47 parallel test and the provider. So I have some doubts about #516 #544 and #608 and I will make the audit there as well. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
