[SLING-6565] Teleporter: Improve bundle names to prevent conflicts in case of uninstall failures

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: JUnit Tests Teleporter 1.0.12
• Fix Version/s: JUnit Tests Teleporter 1.0.14
• Component/s: Apache Sling Testing Rules
• Assignee: Konrad Windszus
• Reporter: Konrad Windszus
• Created: 24/Feb/17 12:09
• Updated: 11/May/17 20:02
• Resolved: 28/Feb/17 12:49

Description

Currently each test bundle gets a unique symbolic name (https://github.com/apache/sling/blob/trunk/testing/junit/teleporter/src/main/java/org/apache/sling/testing/teleporter/client/ClientSideTeleporter.java#L245). That means that in case of uninstallation failures there might be multiple bundles on the same server providing the same JUnit tests. Since it is then not deterministic which bundle is used for executing the test the bundle names should be always the same for the same test class.

The only thing one needs to prevent is parallel execution of those JUnit tests, because each bundle is deployed separately for each test method. If this happens in parallel it may be that one bundle is just uninstalled, while still being in use by he next test. This is a problem already with the current approach, as you cannot tell which bundle is used for executing the test.