[jira] [Commented] (SLING-5452) ClientSideTeleporter should check for web console readiness

["Thierry Ygé (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-5452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276162#comment-15276162 ] 

Thierry Ygé commented on SLING-5452:
------------------------------------

[~bdelacretaz] could this also help to solve SLING-5715 ? I just see the wait is added on install, but nothing is done on uninstall, it would maybe also make sense to check before uninstall as the running test itself may have changed some something in the context, and that can impact the console availability.


> ClientSideTeleporter should check for web console readiness
> -----------------------------------------------------------
>
>                 Key: SLING-5452
>                 URL: https://issues.apache.org/jira/browse/SLING-5452
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: JUnit Tests Teleporter 1.0.6
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: JUnit Tests Teleporter 1.0.8
>
>
> Before installing its test bundle, the {{ClientSideTeleporter}} should (optionally?) check, via HTTP, that the OSGi console is ready to accept it. The customizer could optionally set a longer retry timeout for installing the bundle.
> This is not a problem in our launchpad test suite as the Sling readiness is checked extensively before starting tests, but in smaller test suites it's useful for the teleporter to be self-contained in this respect.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)