[
https://issues.apache.org/jira/browse/SLING-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451868#comment-13451868
]
Felix Meschberger commented on SLING-2595:
------------------------------------------
I think it is not the task of the tests to check for system readyness: They
should assume the system is ready.
Therefore:
* I think the workaround is not needed and the whole check block should be
removed
* The standard test setup in the launchpad should ensure Sling is up before
starting the tests
If the system happens to not be ready when the tests start, they will certainly
fail and thus we are on the "safe" side of not getting false positives.
> Make server ready check for tests optional
> ------------------------------------------
>
> 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
