[SLING-3537] Enable sling testing tools and sling junit remote workflow to refresh packages after bundle install and give the option to uninstall bundles after test

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Affects Version/s: Launchpad Testing 10, JUnit Remote Tests Runners 1.0.10
• Component/s: Testing
• Labels: junit remote sling test
• Environment: Build machine is Windows 64 bit; Execution environment is Adobe CQ 5.6.1
• Assignee: Unassigned
• Reporter: Jordan Black
• Created: 01/May/14 14:31
• Updated: 06/May/23 10:29
• Resolved: 06/May/23 10:29

Description

The current snapshots of sling testing tools (1.0.7-SNAPSHOT) and sling junit remote (1.0.9-SNAPSHOT) were incorrectly failing tests when the same bundles were being deployed to an existing OSGi environment. This was happening because the bundles had the same version number as the bundles that were already installed, and OSGi was getting confused because there was no refresh packages after the install.

So, the current test workflow is this:

• install bundles
• verify bundles are installed
• activate bundles
• start bundles
• run tests
• exit

And I've modified the code to change it to this:

• install bundles
• refresh packages
• verify bundles are installed
• activate bundles
• start bundles
• run tests
• uninstall bundles (optional)
• refresh packages (optional)
• exit

See attached patch file.