I just ran into another issue. The system property "test" is used by the surefire plugin itself. Setting the value to some value (e.g. "integration") and running it on a project will cause it to actually look up the test "integration" and fail if it doesn't exist:
Also see:
https://maven.apache.org/surefire/maven-surefire-plugin/test-mojo.html#test---
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.277 s
[INFO] Finished at: 2017-06-27T14:27:42+02:00
[INFO] Final Memory: 30M/594M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.12.4:test (default-test) on project kapua-build-tools: No tests were executed! (Set -DfailIfNoTests=false to ignore this error.) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
---
