[jira] [Resolved] (SLING-3084) Add forceReload option to JUnitServlet

["Bertrand Delacretaz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SLING-3084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bertrand Delacretaz resolved SLING-3084.
----------------------------------------

    Resolution: Fixed

Implemented in revision 1524717, modified the launchpad integration tests to use it in revision 1524718
                
> Add forceReload option to JUnitServlet
> --------------------------------------
>
>                 Key: SLING-3084
>                 URL: https://issues.apache.org/jira/browse/SLING-3084
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: JUnit Core 1.0.8
>            Reporter: Bertrand Delacretaz
>            Assignee: Bertrand Delacretaz
>            Priority: Minor
>             Fix For: JUnit Core 1.0.10
>
>
> Some TestsProvider services use observation to find out when they must look for new tests, and with Oak that's more asynchronous that it used to be with Jackrabbit.
> As a result, tests might fail as the observation events aren't seen before the HTTP client executes the tests, right after uploading them.
> Adding a forceReload option to the JUnitServlet, which clears all the TestsProvider caches, looks like the best way to solve this - in general we don't need "real-time" detection of new tests, but for automated test suites that's problematic.

--
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