You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2013/10/31 16:09:21 UTC
[jira] [Created] (SLING-3219) ResourceResolverTest should be an
OSGi test case, and use events instead of sleep
Bertrand Delacretaz created SLING-3219:
------------------------------------------
Summary: ResourceResolverTest should be an OSGi test case, and use events instead of sleep
Key: SLING-3219
URL: https://issues.apache.org/jira/browse/SLING-3219
Project: Sling
Issue Type: Bug
Components: Testing
Affects Versions: Launchpad Test Services 2.0.6
Reporter: Bertrand Delacretaz
Assignee: Bertrand Delacretaz
Priority: Minor
The ResourceResolverTest is run in a weird way from a JSP script from the integration-tests module, which makes it a bit hard to debug and prevents it from using JUnit features.
Also, it uses sleep to wait for mapping changes to be activated. This makes it fragile, and it fails sometimes with Oak where observation events are currently (V0.9) delivered less often than in Jackrabbit.
I'll refactor it as a real JUnit test and instead of sleep() use the org/apache/sling/api/resource/ResourceResolverMapping/CHANGED event that the mapping subsystem delivers to indicate mapping changes.
--
This message was sent by Atlassian JIRA
(v6.1#6144)