[SLING-3219] ResourceResolverTest should be an OSGi test case, and use events instead of sleep

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: Launchpad Test Services 2.0.6
• Component/s: Testing
• Assignee: Bertrand Delacretaz
• Reporter: Bertrand Delacretaz
• Created: 31/Oct/13 15:07
• Updated: 31/Oct/13 15:41
• Resolved: 31/Oct/13 15:41

Description

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.

Issue Links

• blocks: SLING-2788 Optionally run Sling on Apache OAK