maven-failsafe-plugin

I've combed StackOverflow and many other sites, have found many other related posts and have followed all said suggestions, but in the end, failsafe is skipping my tests. My JUnit test is located here: myModule/src/main/test/java/ClientAccessIT.java I am skipping surefire because there are no unit tests in this module: <!-- POM snippet --> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-surefire-plugin</artifactId> <configuration> <skip>true</skip> </configuration> </plugin> And I'm trying to run integration tests with failsafe : <!-- POM snippet --> <plugin> <groupId

I've started a new project: PostfixSQLConfig . It's a simple Spring Boot application that is essentialy supposed to provide CRUD access for 4 simple databse tables. I wrote the the repository for the first table and some basic integration tests for said repository. Since this particular table should not provide update functionality, I implemented update function as: @Override public void update(@NonNull Domain domain) throws NotUpdatableException { throw new NotUpdatableException("Domain entities are read-only"); } where NotUpdatableException is my custom exception class. The IT for this code

Do I have to place my integration tests under src/test with the rest of my unit tests and just distinguish them by a pattern such as *Integr*Test , *ITTest , or can they be in src/it (as is the case when developing Maven plugins and using the maven-invoker-plugin )? I'm asking this because, to me it looks not clean enough if both unit and integration tests are in the same place, (even if they were to be controlled via a Maven profile). First maven-fails-plugin runs by default in another life cycle phase (integration-test) as maven-surefire-plugin (test) does. Furthermore you can configurate

It is not completely clear to me how to best use the Maven Failsafe plugin for integration tests. My use case would be to test SQL queries against a local MySQL database. I understand that the database should be started during the pre-integration-test phase, and shut down during the post-integration-test . But how do I specify that? Is there a command line I should put in my pom.xml? Or a method that I should annotate with a specific annotation? Jcs In the regular built-in maven lifecycles (jar, war...) the pre-integration-test and post-integration-test test phases are not bound to any maven

I have a multi-module maven project with both integration and unit tests in the same folder (src/test/java). Integration tests are marked with @Category(IntegrationTest.class) . I want to end up with the following setup: If I run mvn install , I want all tests to compile, but I do not want to execute any. If I run mvn test , I want all tests to compile, but execute only unit tests. If I run mvn integration-test , I want to compile and execute all tests. The important point is, I want this configured in the pom.xml without any extra commandline arguments. Currently I came up with the following

I've a Maven build in which I use the SureFire plugin to run some unit tests, and the FailSafe plugin to run some integration tests. I would like a way to run just the FailSafe plugin's tests. It's not a good solution for me to add different profiles or anything in the pom, because it's a multimodule build and I don't want to have to edit every module's pom. There are skip.tests and maven.test.skip and skipTests which stop all tests, and skipITs , which stops only the failsafe plugin. So, is there a command-line flag for Maven like skipITs , but instead with the functionality of "onlyITs"? I