[
https://issues.apache.org/jira/browse/SLING-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451826#comment-13451826
]
Bertrand Delacretaz commented on SLING-2595:
--------------------------------------------
The tests in question test a Sling instance remotely via http, so they won't
see FRAMEWORK_STARTED or similar events.
Writing to root might not be the best way to find out whether the server is
ready, but whatever changes to that mechanism should not break the integration
tests that run at launchpad/testing. You cannot "just assume that the server is
ready" in such tests, depending on the environment (think overloaded Jenkins
build server) the instance under test might need a while to be up.
> 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
