[
https://issues.apache.org/jira/browse/SLING-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13451860#comment-13451860
]
Carsten Ziegeler commented on SLING-2595:
-----------------------------------------
Please have a look at my committed patch, it just adds a new system property
which by default is not set. If it is set, this test is skipped.
It solves my use cases and leaves by default everything as is
I would be happy to replace the check with something else and more rely on a
push than a pull, but that would be a different issue then :)
> 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
