Difference between revisions of "Equinox p2 tests"

From Eclipsepedia

Jump to: navigation, search
(Tests)
Line 9: Line 9:
  
 
=== Tests ===
 
=== Tests ===
==== Basic install, run and update ====
+
==== Basic install, run and update from Admin UI ====
 
* Using the Admin UI:
 
* Using the Admin UI:
 
** create a new profile  
 
** create a new profile  
Line 21: Line 21:
 
Variation, try with/without exiting the Admin UI.
 
Variation, try with/without exiting the Admin UI.
  
 +
==== Basic install, run and update using remote repository ====
 +
* Using the Admin UI:
 +
** create a new profile
 +
** connect to the test repository
 +
** install the SDK-v1
 +
* Run the provisioned install
 +
* Using the Admin UI:
 +
** look for updates, install eclipse SDK-v2
 +
* Run the provisioned install and verify that the SDK-v2 plugins are here
 +
* Also check that the profile is properly updated in the Admin UI
  
==== Basic install, and update ====
+
==== Basic install/update from Admin UI ====
 
* Using the Admin UI:
 
* Using the Admin UI:
 
** Create a new profile  
 
** Create a new profile  
Line 34: Line 44:
 
Variation, try with/without exiting the Admin UI.
 
Variation, try with/without exiting the Admin UI.
  
 
+
==== Setting up a provisioned SDK that includes the End User UI====
==== Basic install from End User UI ====
+
These steps should be followed to set up an SDK with end user UI.  The provisioned SDK will then be used for all of the End User UI tests.
 
* Using the Admin UI:
 
* Using the Admin UI:
 
** Create a new profile  
 
** Create a new profile  
Line 41: Line 51:
 
** Install the End User UI (The IUs for this can be found on http://download.eclipse.org/eclipse/testUpdates/)
 
** Install the End User UI (The IUs for this can be found on http://download.eclipse.org/eclipse/testUpdates/)
 
* Exit the Admin UI
 
* Exit the Admin UI
 +
 +
==== Install from End User UI====
 
* Start the provisioned install
 
* Start the provisioned install
* Using the End User UI:
+
* Help>Software Updates (Incubation)...
 +
** Find the releng tools in the available features page
 
** Install the releng tools
 
** Install the releng tools
 
* Accept to restart.
 
* Accept to restart.
* Come back up and notice the presence of the releng tools
+
* Notice the presence of the releng tools (should be listed in the installed features page)
 
* Start up the Admin UI
 
* Start up the Admin UI
* Notice the presence of the releng tools in the profile
+
* Notice the presence of the releng tools in the profile  
 
+
  
 
==== Uninstall the releng tools from End User UI ====
 
==== Uninstall the releng tools from End User UI ====
Line 57: Line 69:
 
** Uninstall
 
** Uninstall
 
* Accept the restart
 
* Accept the restart
*Come back up and notice the absence of the releng tools
+
*Come back up and notice the absence of the releng tools (no longer listed in installed features page)
 
*Start up the Admin UI
 
*Start up the Admin UI
 
*Notice the absence of the releng tools in the profile
 
*Notice the absence of the releng tools in the profile
  
 
+
==== Reverting from the End User UI ====
==== Reverting ====
+
 
*Using the Admin UI:
 
*Using the Admin UI:
 
** Create a new profile  
 
** Create a new profile  
 
** Install an SDK
 
** Install an SDK
 +
** Install the End User UI
 +
*Start the provisioned install
 +
** Open the end user UI (Help>Software Updates (Incubation))
 
** Install the releng tools
 
** Install the releng tools
*Start the provisioned install
+
** Verify that the "Installed Features" list shows the releng tools
** verify the presence of the releng tools
+
** Choose "Revert Configuration..." and select a timestamped configuration that does not have the releng tools, Finish
*Using the End User UI:
+
** Verify that the "Installed Features" list no longer shows the releng tools, but still shows the SDK and end user UI
** Uninstall the releng tools
+
** Verify that the "Installed Features" list no longer shows the releng tools
+
** Choose "Revert Configuration" and select a timestamped configuration that had the releng tools
+
** Revert to the configuration and verify that releng tools is now installed.
+
 
+
==== 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 ====
 
==== Bundle pool ====
Line 93: Line 95:
 
* Uninstall the two SDK previously installed
 
* Uninstall the two SDK previously installed
 
* Navigate to the folder of the bundle pool and notice that all the jars and folders are now gone. the GC has run.
 
* Navigate to the folder of the bundle pool and notice that all the jars and folders are now gone. the GC has run.
 
  
 
==== Bundle pool in the eclipse install ====
 
==== Bundle pool in the eclipse install ====
Line 102: Line 103:
 
* Verify that the path in the bundles.txt are relative.
 
* 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
 
* Verify that the path in the osgi.bundles property of the config.ini are relative
 
  
 
==== Manual updates ====
 
==== Manual updates ====
Line 153: Line 153:
 
** remove the bundle from your dropins folder
 
** remove the bundle from your dropins folder
 
** start eclipse and verify that the bundle was uninstalled
 
** start eclipse and verify that the bundle was uninstalled
 
  
 
=== Who, what platform ===
 
=== Who, what platform ===

Revision as of 14:03, 4 February 2008

Contents

Setup

  • To run through all these tests you will need test repositories. There are two ways have repositories:
    • Use the repository available at http://download.eclipse.org/eclipse/testUpdates/. The SDK builds pre-dating december 10th are based on last week I build) and the build dated from the 11th at 09h54.
    • Generate repos for two versions of the eclipse SDK (preferably 3.4 M3 and 3.4 M4 candidate). At generation time make sure to use different versions for the generated SDK's (Use the -rootVersion argument in the launch config to control this).

Throughout the scenarios, SDK-v1 will refer to the oldest version of the two SDKs and SDK-v2 to the newest one.

Also note that contrarily to what we mentioned in the last p2 call, we don't have server zip available yet. We will build those Tuesday morning EDT.

Tests

Basic install, run and update from Admin UI

  • Using the Admin UI:
    • create a new profile
    • install the SDK-v1
  • Run the provisioned install
  • Using the Admin UI:
    • look for updates, install eclipse SDK-v2
  • Run the provisioned install and verify that the SDK-v2 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, run and update using remote repository

  • Using the Admin UI:
    • create a new profile
    • connect to the test repository
    • install the SDK-v1
  • Run the provisioned install
  • Using the Admin UI:
    • look for updates, install eclipse SDK-v2
  • Run the provisioned install and verify that the SDK-v2 plugins are here
  • Also check that the profile is properly updated in the Admin UI

Basic install/update from Admin UI

  • Using the Admin UI:
    • Create a new profile
    • Install the SDK-v1
  • Do *not* start the provisioned install
  • Using the Admin UI:
    • look for updates, install eclipse SDK-v2
  • 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.

Setting up a provisioned SDK that includes the End User UI

These steps should be followed to set up an SDK with end user UI. The provisioned SDK will then be used for all of the End User UI tests.

Install from End User UI

  • Start the provisioned install
  • Help>Software Updates (Incubation)...
    • Find the releng tools in the available features page
    • Install the releng tools
  • Accept to restart.
  • Notice the presence of the releng tools (should be listed in the installed features page)
  • Start up the Admin UI
  • Notice the presence of the releng tools in the profile

Uninstall the releng tools from End User UI

  • From a provisioned install with end user UI
    • Open the end user UI (Help>Software Updates (Incubation))
    • Go to Installed features page
    • Select the releng tools
    • Uninstall
  • Accept the restart
  • Come back up and notice the absence of the releng tools (no longer listed in installed features page)
  • Start up the Admin UI
  • Notice the absence of the releng tools in the profile

Reverting from the End User UI

  • Using the Admin UI:
    • Create a new profile
    • Install an SDK
    • Install the End User UI
  • Start the provisioned install
    • Open the end user UI (Help>Software Updates (Incubation))
    • Install the releng tools
    • Verify that the "Installed Features" list shows the releng tools
    • Choose "Revert Configuration..." and select a timestamped configuration that does not have the releng tools, Finish
    • Verify that the "Installed Features" list no longer shows the releng tools, but still shows the SDK and end user UI

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.
  • Uninstall the two SDK previously installed
  • Navigate to the folder of the bundle pool and notice that all the jars and folders are now gone. the GC has run.

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-v1 (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-v1 (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


Download Resilience

  • From the Admin UI
    • Create a profile
    • Install an SDK and while the download proceeds find an inventive way (a.k.a not using cancel) to abort the download (e.g. unplug the network cable, kill the process, etc.).
    • Restart the installation and see if it completes normally


Dropins Reconciler

  • From the Admin UI
    • Create a profile and install the SDK and User UI
  • For M4 the following manual steps are required.
    • Go to your install folder and edit your eclipse.ini
      • add "-console" at the top.
      • add "-Dorg.eclipse.equinox.p2.reconciler.dropins.directory=C:\ontheside\dropins" to the VM arguments at the bottom
      • Note: The dropin folder must not be inside the profile because of how frameworkadmin adjusts paths to make them relative and a bug with install dir.
      • If you want to collocate your dropins folder you will have to set "-Dosgi.install.area=file:/c:/yourprofile"
    • save and start eclipse
    • at the console "start" the org.eclipse.equiniox.p2.reconciler.dropins bundle
    • exit eclipse
  • Testing
    • put a bundle in your dropins folder
    • start eclipse and verify that the bundle was installed
    • exit eclipse
    • remove the bundle from your dropins folder
    • start eclipse and verify that the bundle was uninstalled

Who, what platform

  • Pascal, MacOs, XP
  • Andrew, Linux (gtk 2.12.1)
  • DJ, Linux
  • John, Vista, Windows XP
  • Simon, Windows XP
  • Allan, XP
  • Susan, Windows XP