You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2017/08/30 09:11:02 UTC

[jira] [Created] (OAK-6599) Review testcases which do not confirm to Maven test pattern

Chetan Mehrotra created OAK-6599:
------------------------------------

             Summary: Review testcases which do not confirm to Maven test pattern 
                 Key: OAK-6599
                 URL: https://issues.apache.org/jira/browse/OAK-6599
             Project: Jackrabbit Oak
          Issue Type: Task
            Reporter: Chetan Mehrotra
            Assignee: Chetan Mehrotra
            Priority: Minor
             Fix For: 1.8


[~diru] highlighted in OAK-6598 that some test in Oak do not confirm to Maven test pattern and hence are not executed in builds done from Maven.

From [1] and [2] by default test with following pattern are considered as test by Maven
{noformat}
"**/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".
"**/*TestCase.java" - includes all of its subdirectories and all java filenames that end with "TestCase".

Integration test

"**/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".
{noformat}

We should identify such test and rename them to confirm to the pattern

[1] http://maven.apache.org/surefire-archives/maven-surefire-2.15/maven-surefire-plugin/examples/inclusion-exclusion.html
[2] http://maven.apache.org/surefire/maven-failsafe-plugin/examples/inclusion-exclusion.html



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)