You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2013/02/19 18:45:13 UTC

[jira] [Resolved] (SLING-2544) Restore tests included in the no longer existing JcrResourceResolverTest

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

Carsten Ziegeler resolved SLING-2544.
-------------------------------------

    Resolution: Fixed

I've moved all tests into server side tests, some of them into jsps and the majority into a test class which is triggered by a jsp.
This move revealed several problems of the tests: mainly they were not cleaning up after they run. I've fixed this now and the state of the repository should be the same as before the tests run.

As changes to aliases and mappings are processed asynchronously, I've added some sleeps in the test which result in a longer test run - but for now it's better to have a longer running time than failing tests :)
                
> Restore tests included in the no longer existing JcrResourceResolverTest 
> -------------------------------------------------------------------------
>
>                 Key: SLING-2544
>                 URL: https://issues.apache.org/jira/browse/SLING-2544
>             Project: Sling
>          Issue Type: New Feature
>          Components: Launchpad, ResourceResolver, Testing
>            Reporter: Antonio Sanso
>            Assignee: Justin Edelson
>             Fix For: Launchpad Testing 7
>
>         Attachments: JcrResourceResolverTest.java, SynchronousJcrResourceListener.java
>
>
> With SLING-2396 almost all the testsincluded in the no longer existing JcrResourceResolverTest e.g. testResolveVirtualHostHttp80()/ testResolveResourceAlias()/ ... have been "lost in translation".
> I think it would be really useful to restore them specially for regression detection

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