Skip to content

Maven Failsafe Plugin is always skipping integration tests

I am attempting to configure my Maven project to have unit tests and integration tests. The unit tests are already working fine using the Maven Surefire plugin and are named according to the pattern *

After adding the Failsafe plugin, like so:


I added an integration test named However, when I run:

mvn failsafe:integration-test

I get the following:

[INFO] Scanning for projects...
[INFO] ------------------------------------------------------------------------
[INFO] Building MyApp 1.0
[INFO] ------------------------------------------------------------------------
[INFO] --- maven-failsafe-plugin:2.18.1:integration-test (default-cli) @ MyApp ---
[INFO] Tests are skipped.
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.368 s
[INFO] Finished at: 2015-03-04T14:43:50-06:00
[INFO] Final Memory: 11M/219M
[INFO] ------------------------------------------------------------------------

My test class (buried a few package levels deep beneath the test hierarchy) looks something like:


import org.junit.Test;
import org.junit.Assert;

import org.junit.runner.RunWith;
import org.springframework.test.context.junit4.SpringJUnit4ClassRunner;
import org.springframework.beans.factory.annotation.Autowired;

public class SomeTestIT
    private SomeService target;

    public void testTest()

    public void basicListTest()

Where the tests are stubs to make sure that I have the Maven integration working.

I have ensured that:

  • My POM includes a direct, test scoped dependency on JUnit.
  • I have tried the plugin configuration both with and without an explicit test runner dependency.
  • I have tried the configuration above both with and without an explicit include pattern (on the assumption that my class ought to have been picked up by the defaults).

Nonetheless, the tests never actually run. Is there anything else necessary to get the integration tests running?



I finally figured out what was going on and wanted to keep anyone else from spinning their wheels like I did. In the <properties> tag at the head of the POM, someone had added a property that read <skipITs>true</skipITs>. There were no integration tests previously, so the property was useless. It was probably cargo-culted out of some other POM without any real regard for what it is or what it does.

7 People found this is helpful