You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By default, the maven failsafe plugin includes tests with the following naming schemes (see documentation):
**/IT*.java - includes all of its subdirectories and all Java filenames that start with "IT".
**/*IT.java - includes all of its subdirectories and all Java filenames that end with "IT".
**/*ITCase.java - includes all of its subdirectories and all Java filenames that end with "ITCase".
Problem
By default, the Citrus admin UI sets filters on (copied from the default citrus-project.json):
This is inconsistent with the default failsafe settings and will filter out tests which are correctly named integration tests, e.g. ITSomeIntegrationTest.java/xml (which is my naming scheme).
Moreover, some unit tests (which by default are run by surefire) are included in the Citrus admin UI.
According to the maven surefire documentation, the following naming schemes are included by default:
**/Test*.java - includes all of its subdirectories and all Java filenames that start with "Test".
**/*Test.java - includes all of its subdirectories and all Java filenames that end with "Test".
**/*Tests.java - includes all of its subdirectories and all Java filenames that end with "Tests".
**/*TestCase.java - includes all of its subdirectories and all Java filenames that end with "TestCase".
Solution
Adhere to the defaults set by the plugins which actually run the tests.
If unit tests which run with surefire should be executed at all (by default) by the Citrus UI is debatable.
The text was updated successfully, but these errors were encountered:
Background
By default, the maven failsafe plugin includes tests with the following naming schemes (see documentation):
Problem
By default, the Citrus admin UI sets filters on (copied from the default
citrus-project.json
):This is inconsistent with the default failsafe settings and will filter out tests which are correctly named integration tests, e.g.
ITSomeIntegrationTest.java/xml
(which is my naming scheme).Moreover, some unit tests (which by default are run by surefire) are included in the Citrus admin UI.
According to the maven surefire documentation, the following naming schemes are included by default:
Solution
Adhere to the defaults set by the plugins which actually run the tests.
If unit tests which run with surefire should be executed at all (by default) by the Citrus UI is debatable.
The text was updated successfully, but these errors were encountered: