Details
-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
11.2
-
None
-
Unknown
-
N/A
-
N/A
-
Description
It seems we cannot use -Dtest or -Dpattern in command line to filter a unique test class to execute in docker test.
Using mvn clean install -Dtest=AttachmentIT seems to trigger
the right test class, but then AllIT test suite is also called.
Here's an excerpt of the Maven log obtained in that case (full log attached):
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 132.944 s - in org.xwiki.flamingo.test.ui.AttachmentIT [INFO] [INFO] Results: [INFO] [INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] [INFO] --- maven-jar-plugin:3.1.1:jar (default-jar) @ xwiki-platform-flamingo-skin-test-docker --- [INFO] Building jar: /home/urli/Github/xwiki-platform/xwiki-platform-core/xwiki-platform-flamingo/xwiki-platform-flamingo-skin/xwiki-platform-flamingo-skin-test/xwiki-platform-flamingo-skin-test-docker/target/xwiki-platform-flamingo-skin-test-docker-11.3-SNAPSHOT.jar [INFO] [INFO] --- maven-failsafe-plugin:2.22.0:integration-test (functional-tests) @ xwiki-platform-flamingo-skin-test-docker --- [INFO] [INFO] ------------------------------------------------------- [INFO] T E S T S [INFO] ------------------------------------------------------- [INFO] Running org.xwiki.flamingo.test.ui.AllIT 16:12:46.668 [main] INFO o.x.t.d.i.j.XWikiDockerExtension - XWiki is not started, starting all...