Based what you’ve written it sounds like you didn’t named your integration tests correctly and you didn’t use the maven-failsafe-plugin for your integration tests. Based on the convention of the maven-failsafe-plugin you should name your integration tests like *IT.java. If you named your integration tests appropriately you can handle that with a more or less … Read more
Maven knows two types of parameters for skipping tests: -Dmaven.test.skip=true or -DskipTests=true The surefire-plugin documentation only mentions the first one, which you have not tried yet.
Official way with selecting providers. You can also specify multiple providers as dependencies, and they will all be run and produce a common report. This may be especially handy with external providers, since there are few use-cases for combining the included providers. <plugin> <artifactId>maven-surefire-plugin</artifactId> <version>2.18.1</version> <dependencies> <dependency> <groupId>org.apache.maven.surefire</groupId> <artifactId>surefire-junit47</artifactId> <version>2.18.1</version> </dependency> <dependency> <groupId>org.apache.maven.surefire</groupId> <artifactId>surefire-testng</artifactId> <version>2.18.1</version> … Read more
If you’re using the Maven failsafe plugin, you can run a single integration test by setting the it.test property to your fully qualified test class name: mvn -D it.test=your.TestCase verify See the failsafe plugin docs for more info.
You can add -Dmaven.test.failure.ignore=false to the MAVEN_OPTS if you click on Advanced button in the Build section of your Jenkins Job. See Maven Surefire Plugin – surefire:test options for reference.
Workaround for the issue was to override Spring Boot’s maven-surefire-plugin definition and set useSystemClassLoader to false. Read Surefire docs for more details <build> <plugins> … <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <configuration> <useSystemClassLoader>false</useSystemClassLoader> </configuration> </plugin> </plugins> </build>
Better you start with https://maven.apache.org/surefire/maven-surefire-plugin/ In short link says: The Surefire Plugin is used during the test phase of the build lifecycle to execute the unit tests of an application. It generates reports in two different file formats Plain text files (.txt) XML files (.xml)
It sounds like you didn’t understand the concept of the build life-cycle in Maven. If you run mvn install all life-cycle phases (including the install phase itself) run before the install phase. This means running the following phases: validate initialize generate-sources process-sources generate-resources process-resources compile process-classes generate-test-sources process-test-sources generate-test-resources process-test-resources test-compile process-test-classes test prepare-package package … Read more
Try using @{argLine} instead of ${argLine} (or surefire.argLine in your case) It allows surefire to read a property as modified by other plugins instead of reading the one substituted by Maven itself. Then you can set the argLine param to empty in Maven properties: <properties> <argLine></argLine> </properties> Which now will not cause any problems. More … Read more
Maven has since been updated and can use categories. An example from the Surefire documentation: <plugin> <artifactId>maven-surefire-plugin</artifactId> <version>2.11</version> <configuration> <groups>com.mycompany.SlowTests</groups> </configuration> </plugin> This will run any class with the annotation @Category(com.mycompany.SlowTests.class)