Equinox p2 tests

Setup

• Generate metadata/artifact repos for the eclipse SDK 3.4 M2 and eclipse SDK 3.4 M3 in the same repos.

Tests

Basic install, run and update

• Using the Admin UI:
  • create a new profile
  • install the SDK 3.4 M2
• Run the provisioned install
• Using the Admin UI:
  • look for updates, install eclipse SDK 3.4 M3
• Run the provisioned install and verify that the M3 plugins are here
• Also check that the profile is properly updated in the Admin UI

Variation, try with/without exiting the Admin UI.

Basic install, and update

• Using the Admin UI:
  • Create a new profile
  • Install the SDK 3.4 M2
• Do *not* start the provisioned install
• Using the Admin UI:
  • look for updates, install eclipse SDK 3.4 M3
• Run and verify that the plugins have been changed
• Also check that the profile is properly updated in the Admin UI

Variation, try with/without exiting the Admin UI.

Basic install from End User UI

• Using the Admin UI:
  • Create a new profile
  • Install the SDK 3.4 M2
  • Install the End User UI
• Exit the Admin UI
• Start the provisioned install
• Using the End User UI:
  • Install the releng tools
• Accept to restart.
• Come back up and notice the presence of the releng tools
• Start up the Admin UI
• Notice the presence of the releng tools in the profile

Install the releng tools

• Using the Admin UI:
  • Create a new profile
  • Install the SDK 3.4 M2
  • Install the End User UI
• Exit the Admin UI
• Start the provisioned install
• Using the End User UI:
  • install the releng tools
• Accept to restart.
• Come back up and notice the presence of the releng tools
• Start up the Admin UI
• Notice the presence of the releng tools in the profile

Reverting

• Using the Admin UI:
  • Create a new profile
  • Install an SDK
  • Install the releng tools
• Start the provisioned install
  • verify the presence of the releng tools
• Using the Admin UI:
  • Revert to the state where releng tools was not installed
• Start the provisioned install
  • verify the absence of the releng tools

Install from a remote repository

• Using the Admin UI:
  • Create a new profile
  • Point your repos to the repositories produced during the build
  • Install the SDK
• Start the provisioned install

Bundle pool

• Using the Admin UI:
  • Create a new profile
  • Install the SDK. During the installation notice the dialog saying that around 150M (the size of the SDK) should be "installed" (caveat, this may already be giving you the same result than in the second step if you are installing an already installed SDK.)
• Create a second profile
• Install the SDK in it
  • During the installation notice the dialog saying that only around 50K should be "installed".
  • Notice that the download phase goes much faster.

Bundle pool in the eclipse install

• Using the Admin UI:
  • Create a new profile: in the dialog set the install folder and the bundle pool to the same location. It will be the root of your eclipse install.
• Install the SDK
• Verify that the plugins folder is located at a subfolder of the install location
• Verify that the path in the bundles.txt are relative.
• Verify that the path in the osgi.bundles property of the config.ini are relative

Manual updates

• From the Admin UI
  • Create a profile
  • Install the SDK 3.4 M2 (or any version for which you will have an update in the repository)
  • Install the User UI
• Start the provisioned SDK
  • Go to the end user UI (Help>Software Updates (Incubation)
  • On the installed features page, push the "Check for Updates" button
  • You should get a dialog showing the newer version
  • Accept the update, restart
  • Verify that the end user UI now shows the new version in the installed features list

Automatic updates

• From the Admin UI
  • Create a profile
  • Install the SDK 3.4 M2 (or any version for which you will have an update in the repository)
  • Install the User UI
• Start the provisioned SDK
  • Go to the update preference and enable the auto update
  • Wait for a notification to show up
  • Accept the install, restart