Package org.apache.maven.surefire.its.jiras
package org.apache.maven.surefire.its.jiras
-
ClassDescription"verify" goal ignores "dependenciesToScan" parameter when checking tests existencePlugin Configuration: parallel=classes
With Surefire 2.15$ mvn test -Dtest=MyTest#testFooResults: Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
With Surefire 2.16$ mvn test -Dtest=MyTest#testFoo
Results: Tests run: 0, Failures: 0, Errors: 0, Skipped: 0SUREFIRE-1041: An error in a JUnit runner should not lead to an error in SurefireSUREFIRE-1055 Correct test count in parallel run mode.Description of SUREFIRE-1080:
There are 9 tests in total in the attached project, and mvn test will show 9 tests run.The purpose of this IT is to assert that the run order of test classes is according to the settings:Test surefire-report on TestNG testSUREFIRE-1136 Correct current working directory propagation in forked mode Note: variables expansion behaves differently on MVN 2.x since not existing variables are resolved to 'null' value so that ${surefire.forkNumber} cannot work.Test that runtime reported on console matches runtime in XMLSUREFIRE-1152 Assert rerunFailingTestsCount works with test suitesIT for https://issues.apache.org/jira/browse/SUREFIRE-1177Fix for TestNG parameter -dataproviderthreadcount.Surefire 2.19 spawns unnecessary tests in surefire-junit4 provider.Allow rerunFailingTestsCount, skipAfterFailureCount togetherAdded included pattern Tests.java.Test the group filter for TestNGhttps://issues.apache.org/jira/browse/SUREFIRE-1295 https://github.com/apache/maven-surefire/pull/136Report XML should contain system properties of forked JVM.SUREFIRE-613 Asserts proper test counts when running in parallelTest https://issues.apache.org/jira/browse/SUREFIRE-1426Test Surefire-146 (forkMode=pertest fails to call setUp)Test charset provider (SUREFIRE-162)See the JIRA https://issues.apache.org/jira/browse/SUREFIRE-1712Integration test for SUREFIRE-1733.Integration test for SUREFIRE-1733.Test Surefire-224 (XML test reports are not well-formed when failure message contains quotes)Test TestNG setup and teardown ordering with parallelismVerify that Surefire adds Maven dependencies to the Module Path if theyprovidea service that isuse'd by another JPMS module that is already on the Module Path.Test for shadefire usageIntegration Tests for SUREFIRE-2036Test Surefire-224 (XML test reports are not well-formed when failure message contains quotes)Test Surefire-257 Verifies that surefire does not re-run tests in site buildTest Surefire-570 Multiple report directoriesSUREFIRE-621 Asserts proper test counts when running junit 3 tests in parallelTest Surefire-376 (TestNG @AfterSuite failures are ignored)SUREFIRE-377 (When JUnit and TestNG tests are in same project, only one set gets run).SUREFIRE-613 Asserts proper test counts when running in parallelTest JUnit test that contains inner classesTest JUnit test that contains inner classesSUREFIRE-500 Asserts correct error handling for the "odd" surefire-500 (and 625) issues.SUREFIRE-621 Asserts proper test counts when running junit 3 tests in parallelSUREFIRE-569 Add support for scanning Dependencies for TestClassesTest Surefire-570 Multiple report directoriesSUREFIRE-613 Asserts proper test counts when running in parallelSUREFIRE-621 Asserts proper test counts when running junit 3 tests in parallel
SUREFIRE-1264 Some tests can be lost when running in parallel with parameterized tests
Removed decision making with JUnit3 inTestSetclass during Jira activity ofSUREFIRE-1264which results in one hot spot where the test class is determined (see JUnitCoreRunListener#fillTestCountMap()).Asserts that console output always goes somewhere ;)SUREFIRE-634 Verifies error message on unsettable system propertiesSUREFIRE-673 Asserts that a given mockito build works as it should (classloader problem in 2.7)SUREFIRE-674 Asserts that the build fails when tests have errorsSUREFIRE-674 Asserts that the build fails when tests have errorsSUREFIRE-685 Asserts that only the specified tests are run with comma separated includesSUREFIRE-697 Asserts proper truncation of long exception messages Some say testing this is a bit over the top.TestTest Surefire-740 Truncated comma with non us localeTest Surefire-740 Truncated comma with non us localeTest Surefire-740 Truncated comma with non us localeTest Surefire-740 Truncated comma with non us localeTest Surefire-740 Truncated comma with non us localeTestSUREFIRE-818Failsafe should work with early return when no tests s