[
https://issues.apache.org/jira/browse/SLING-2197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-2197.
----------------------------------------
Resolution: Fixed
Fixed in revision 1169713, still using the webconsole "API" until we get
something better.
All the code that interfaces with the webconsole is in the WebconsoleClient
class, so easy to rewrite when an official RESTful API becomes available.
[1]
http://svn.apache.org/repos/asf/sling/trunk/testing/tools/src/main/java/org/apache/sling/testing/tools/osgi/WebconsoleClient.java
> 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
> Reporter: Bertrand Delacretaz
> Assignee: Bertrand Delacretaz
>
> 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
