[OAK-6599] Review testcases which do not confirm to Maven test pattern

• Type: Task
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 1.7.7, 1.8.0
• Component/s: core, lucene
• Assignee: Chetan Mehrotra
• Reporter: Chetan Mehrotra
• Created: 30/Aug/17 09:10
• Updated: 14/Sep/17 13:01
• Resolved: 31/Aug/17 08:27

Description

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

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

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