You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2011/09/12 14:53:12 UTC

[jira] [Updated] (SLING-2197) Sling testing tools: verify that all bundles are started after installing them

     [ https://issues.apache.org/jira/browse/SLING-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz updated SLING-2197:
---------------------------------------

    Affects Version/s: Sample Integration Tests 1.0.6
                       org.apache.sling.testing.tools 1.0.4
        Fix Version/s: org.apache.sling.testing.tools 1.0.6
                       Sample Integration Tests 1.0.8

> Sling testing tools: verify that all bundles are started after installing them
> ------------------------------------------------------------------------------
>
>                 Key: SLING-2197
>                 URL: https://issues.apache.org/jira/browse/SLING-2197
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: Sample Integration Tests 1.0.6, org.apache.sling.testing.tools 1.0.4
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>             Fix For: Sample Integration Tests 1.0.8, org.apache.sling.testing.tools 1.0.6
>
>
> After installing additional bundles, the SlingTestBase class should check that they are all started, try to start those that are not, and exit only once they are all started or a time out occurs.
> Best might be to add the following methods to the WebconsoleClient class:
> startBundle(String symbolicName)
> String getBundleState(String symbolicName)
> startAllBundles(String ...symbolicName)
> And use those new methods in the SlingTestBase class.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira