[SLING-5352] TeleporterRule test bundles should be installed once per test class only

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: JUnit Tests Teleporter 1.0.4
• Component/s: Testing
• Assignee: Bertrand Delacretaz
• Reporter: Thierry Ygé
• Created: 05/Dec/15 16:52
• Updated: 05/Sep/18 09:17

Description

Currently it's not possible to use the TeleporterRule as Rule and ClassRule annotation.

The idea is that BeforeClass will create the bundle and install it.
AfterClass will uninstall it. This will optimize the processing and avoid a lot of round trip and waits. It still allow to use it as in the original version with only Rule annotation.

I have made some test , and will attach my suggested solution. It allow to use it as before:

    @Rule
    public TeleporterRule classRule = TeleporterRule.forClass(SomeMoreTest.class, "Launchpad");

or as follow with a ClassRule annotation:

    @ClassRule
    public static TeleporterRule classRule = TeleporterRule.forClass(SomeTest.class, "Launchpad");

    @Rule
    public TeleporterRule teleporterRule = classRule;

The changes are not so big, it only need a static field to store the bundle symbolic name value in the case it is used with the ClassRule annotation. Then adapt the logic in the statement to differentiate between ClassRule and Rule usages.

Issue Links

• relates to: SLING-5369 Update to JUnit 4.12