[
https://issues.apache.org/jira/browse/SLING-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451822#comment-13451822
]
Felix Meschberger commented on SLING-2595:
------------------------------------------
IIRC that startup check was introduced to prevent starting tests before Sling
was ready to process requests. Maybe it was even at a time where declarative
services processing was asynchronous and thus the FRAMEWORK_STARTED event was
fired before the system was actually up and running.
Nowadays, the FRAMEWORK_STARTED event is only fired when the initial start
level is reached and DS has done all its processing.
Hence: Do we still need that check at all ?
> Tests should not check if the server is ready
> ---------------------------------------------
>
> Key: SLING-2595
> URL: https://issues.apache.org/jira/browse/SLING-2595
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Commons Testing 2.0.10
> Reporter: Carsten Ziegeler
> Fix For: Commons Testing 2.0.12
>
>
> Right now if you extend the HttpTestBase each and every test checks whether
> the server is up and running. This is done by writing to the root of the
> repository. Once some security is in place and writing to root is not
> possible, all tests fail.
> I think it shouldn't be the task of the tests to check if the server is
> running, they should simply assume the server is available.
> The simplest solution for now would be to make this check configurable by a
> system property
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
