You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2015/09/09 14:15:45 UTC
[jira] [Updated] (SLING-4819) Allow to automatically undeploy all
deployed bundles after execution of ITs
[ https://issues.apache.org/jira/browse/SLING-4819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus updated SLING-4819:
-----------------------------------
Attachment: SLING-4819-testingtools-v01.diff
SLING-4819-junitremote-v01.diff
Attached are two patches
1. the junitremote patch will allow to optionally undeploy bundles (if the {{SlingRemoteTestRunner}} is used. For that a method annotated with @After has been added to {{SlingTestBase}}
2. the testingtools patch will extend the {{SlingRemoteTestRunner}} so that all methods annotated with @After are automatically called (used for the uninstallation of the bundles but might be handy for other stuff as well).
[~bdelacretaz] Can you have a look at those patches?
> Allow to automatically undeploy all deployed bundles after execution of ITs
> ---------------------------------------------------------------------------
>
> Key: SLING-4819
> URL: https://issues.apache.org/jira/browse/SLING-4819
> Project: Sling
> Issue Type: Improvement
> Affects Versions: org.apache.sling.testing.tools 1.0.10
> Reporter: Konrad Windszus
> Attachments: SLING-4819-junitremote-v01.diff, SLING-4819-testingtools-v01.diff
>
>
> Through the property {{sling.additional.bundle}} it is already possible to deploy bundles before running integration tests derived from {{SlingTestBase}}.
> It should also be supported to automatically undeploy those bundles after the test has finished.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)