[
https://issues.apache.org/jira/browse/SLING-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konrad Windszus resolved SLING-6565.
------------------------------------
Resolution: Fixed
Fix Version/s: JUnit Tests Teleporter 1.0.14
Fixed with [r1784734|http://svn.apache.org/r1784734].
> Teleporter: Improve bundle names to prevent conflicts in case of uninstall
> failures
> -----------------------------------------------------------------------------------
>
> Key: SLING-6565
> URL: https://issues.apache.org/jira/browse/SLING-6565
> Project: Sling
> Issue Type: Improvement
> Components: Apache Sling Testing Rules
> Affects Versions: JUnit Tests Teleporter 1.0.12
> Reporter: Konrad Windszus
> Assignee: Konrad Windszus
> Priority: Minor
> Fix For: JUnit Tests Teleporter 1.0.14
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
