It is stateful report and won't work if re-run or parallel executions send test events out of order. (4) StatelessXmlReporter repeatedly generates XML report. (3) Fire and consume more events (normal run start/end, re-run start/end) TestSetRunListener should only forward events to multiple reporters. (2) TestSetRunListener should not cache test event and make any guess about the impl in StatelessXmlReporter. (ready for parameterized tests and a coherent re-run) (1) We will identify the test by UniqueId in SimpleReportEntry and not by the traditional combination of class/method name. Polymorphism for remote and local process communication. It is internally used to switch over the pipes and TCP connector. Provided extensions which can be used to customize this interprocess communication in plugin configuration. New interprocess communication with TCP/IP which fixed current blocker and critical bugs. Test Report tasks (prerequisite: SUREFIRE-1222 in 3.0.0-M4) Provided bug fixes for Docker Alpine/BusyBox Linux, JUnit5 and 43 more.įorkClient attempts to consume unrelated lines The impl is located in a center point and it is a prerequisite in next versions. We reworked the internal implementation so that new commands and events can be easily added. Provided 3 extensions of reporters which can be used to customize XML report, console and file reporters. See the Release Notes for the version 3.0.0-M3 Smart stacktrace in test summary should not print JUnit5 assertion exception type JUnit Runner that writes to System.out corrupts Surefire's STDOUT when using JUnit's Vintage Engine Maven-surefire-report-plugin fails on JDK 11
See the Release Notes for the version 3.0.0-M2įixed: maven-surefire-report-plugin supports JDK11, JUnit5 issues, deprecated skipTests in Failsafe plugin, used ShadeFire 3.0.0-M2 Plugin fails if used Toolchains together with JDK9+ and (Jigsaw) modular paths (module-info.java)įeature: Option to switch-off Java 9 modules Surefire fails loading class ForkedBooter when using a sub-directory pom file Windows slashes appear in relative paths of Class-Path in MANIFEST.MF (Boot Manifest-JAR) See the Release Notes for the version 3.0.0-M1įixed: JDK9 and Windows Class-Path issues, 3.0 and Legacy Report XSD, 3.0.0-M2 shadefireįixed JDK9+ (Jigsaw) modular paths (module-info.java) having white spaces on file system Surefire manifest jar classloading broken on latest Debian/Ubuntu Java8 This is the road map of the development, see the GH. Due to wrong formatting of console text messages in Maven Version prior to 3.1.0 it is highly recommended to use Maven 3.1.0 or higher. Requirements: Maven 3.x and JDK 1.7 or higher. Run tests in a different JVM using toolchains.Fork Options and Parallel Test Execution.
0 kommentar(er)
