[SLING-3181] Use the *IT.java name pattern to separate between unit and integration tests

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Component/s: Best practices
• Assignee: Unassigned
• Reporter: Bertrand Delacretaz
• Created: 16/Oct/13 13:07
• Updated: 04/May/23 09:23
• Resolved: 04/May/23 09:23

Description

When a module contains both unit and integration tests, naming integration test classes *IT allows the surefire and failsafe plugins to automatically select the right tests, without requiring pom configurations.

In the bundles/scripting/core module for example, the BindingsValuesProvidersByContextIT test is run in the integration-tests phase, and other tests in the test phase, based only on the test names:

src/test/java/org/apache/sling/scripting/core/impl/BindingsValuesProvidersByContextIT.java
src/test/java/org/apache/sling/scripting/core/impl/DummyScriptEngineFactory.java
src/test/java/org/apache/sling/scripting/core/impl/helper/ProtectedBindingsTest.java
src/test/java/org/apache/sling/scripting/core/impl/LogWriterTest.java
src/test/java/org/apache/sling/scripting/core/impl/ScriptEngineManagerFactoryTest.java