[
https://issues.apache.org/jira/browse/SLING-3537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jordan Black updated SLING-3537:
--------------------------------
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.
was:
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.
> Enable sling testing tools and sling junit remote workflow to refresh
> packages after bundle install and give the option to uninstall bundles after
> test
> -------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SLING-3537
> URL: https://issues.apache.org/jira/browse/SLING-3537
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Launchpad Testing 7, JUnit Remote Tests Runners 1.0.10
> Environment: Build machine is Windows 64 bit
> Execution environment is Adobe CQ 5.6.1
> Reporter: Jordan Black
> Labels: junit, remote, sling, test
> Attachments: uninstall-and-refresh-bundles.patch
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
