[MBUILDCACHE-72] instructions for running failsafe plugin

**[Adrian Herscu](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=adrian.herscu@gmail.com)** opened **[MBUILDCACHE-72](https://issues.apache.org/jira/browse/MBUILDCACHE-72?redirect=false)** and commented

For system test automation we use the Failsafe Plugin.

In a very small automation project it takes about 20 seconds from launching Maven until the tests actually begin.

If the cache is configured, such as that Failsafe always runs, then after cleaning, it fails because no classes are in target directory.

If Failsafe is not configured to always run, then no testing is done unless something is changed in the sources.

It appears that in both cases, it makes no sense for using the build cache, although it could speed execution by preventing what it was meant to prevent 

It would be great to have more details if the build cache can be used for such scenario, and cut down the start time.

---

1 votes, 2 watchers

Start by reviewing the Maven Failsafe Plugin configuration and how the build cache interacts with clean builds and source changes. Reproduce the described behavior in a small automation project, then document whether the build cache supports this scenario and how to configure it without skipping tests or failing when target contains no classes.

Written by the indexing model from the issue text.