Difference between revisions of "Equinox/p2/UI Manual Tests"

Revision as of 13:24, 15 September 2008

Sanity Tests

These tests can be run quickly every time you take a new build.

Sanity Test of Installed Features

• Switch to Installed Software Page
• You should see one entry for the SDK

Sanity checking of the repositories

• Try adding different sites #Test Sites in different ways.
  • Drag URL's from browsers to different targets
    • Available software page
    • Repository dialog (Manage sites...)
    • Add site dialog entry field
  • Drag folders from platform browsers to same targets (may not work on Mac and Unix, please annotate https://bugs.eclipse.org/bugs/show_bug.cgi?id=223991 with your findings)
  • Use the archive button in the add site dialog to add a jar or zip
  • Use the local button in the add site dialog to add a folder
• Use the manage sites dialog to disable some sites
  • Verify that the content of disabled sites is no longer showing

Sanity Test of Available Software Page

• Toggle the [ ] Show only latest versions
  • Verify that this controls whether all versions or only the latest are shown for an IU.
• Toggle the [ ] Include items that have already been installed
  • Installed items should disappear when you toggle this. If all versions are showing, the installed version disappears but the other IU versions show
• Switch between site, category, and name view
• Switch back to your assigned view
• Type "releng" in the filter box, it should appear in bold in site or category view, plain in name view
• Select releng and look at the properties, verify that property pages look right

Test Sites

• p2 update sites in jar format
  • http://download.eclipse.org/releases/ganymede
  • http://download.eclipse.org/tools/mylyn/update/e3.4/content.jar
• p2 update sites in xml format
• update manager sites
  • http://www.polarion.org/projects/subversive/download/eclipse/2.0/update-site/
  • http://update.eclemma.org
  • http://findbugs.cs.umd.edu/eclipse
• update manager sites with install handlers
  • http://www.developer.com/img/2007/03/upd-install-site.xml
• local archived p2 site
• local folders with an eclipse/features, eclipse/plugins dir structure (post zip here for expansion on local drive)

Test Passes

There are several different preferences/modes that drive the UI, so we have assigned user groups to run with different preference settings. Some of the tests will have you switch some of the toggles or prefs, but this is the mode you should run otherwise. Some of the tests are sequential, to keep setup to a minimum. If one test leaves you with a wizard open, leave it open and read the next test before closing it. The next test might involve that same wizard.

Test Pass Groups

• User Group A -
  • Preferences
    • Automatic Updates - Auto updates on, Look for Updates each time platform is started, Search for updates and notify when available, Notify every 30 minutes
    • Updating from the file system - use defaults
  • Available Software - view by site, [X] show only latest versions, [ ] Include items that have already been installed

• User Group B -
  • Preferences
    • Automatic Updates - Auto updates on, Look for Updates each Tuesday at... (use a time that will trigger during the test pass), Download new updates automatically, Notify me once
    • Updating from the file system - use defaults
  • Available Software - view by category, [X] show only latest versions, [ ] Include items that have already been installed

• User Group C -
  • Preferences
    • Automatic Updates - Auto updates off
    • Updating from the file system - use defaults
  • Available Software - view by name, [ ] show only latest versions, [X] Include items that have already been installed

Test Matrix

Each tester has an assigned platform and UI group.

• Pascal, MacOs, XP, UI group A
• Andrew, Linux (gtk 2.12.1), UI group B
• DJ, Linux, UI group C
• John, Vista, Windows XP, UI group A
• Simon, Windows XP, UI group B
• Susan, Windows XP, UI group C

Setup

• Start with a clean SDK
• The update tests require an SDK later than what you've already provisioned.
• Use a fresh workspace so that dialog settings, prefs, and remembered licenses start with the defaults
• Window>Preferences>Install/Update>Automatic Updates
  • Set the preferences according to your user group
• Help >Software Updates
  • Switch to Available Software Page
  • Set the view mode and check boxes for your user group

Sanity Test of Installed Features

• Switch to Installed Software Page
• You should see one entry for the SDK

Add the test updates site using drag

• Switch to Available Software Page
• Drag this link to the available software page: http://download.eclipse.org/eclipse/testUpdates/
• It may take a little time to refresh the view, now check
  • Group A - The site should be selected and expanded once the view is refreshed
  • Group B - The categories for the site should appear
  • Group C - The IU's in the site should appear

Sanity Test of Available Software Page

• Toggle the [ ] Show only latest versions
  • Verify that this controls whether all versions or only the latest are shown for an IU.
• Toggle the [ ] Include items that have already been installed
  • Installed items should disappear when you toggle this. If all versions are showing, the installed version disappears but the other IU versions show
• Switch between site, category, and name view
• Switch back to your assigned view
• Type "releng" in the filter box, it should appear in bold in site or category view, plain in name view
• Select releng and look at the properties, verify that property pages look right

Install from End User UI

• Check mark the releng tools in the Available Software list
• The install button should enable
• Click the button and review choices in the wizard
• Unchecking the box in the wizard should show an error
• Check box again. You should have a gray finish button because releng tools has a license
• Click "Next" and accep the license
• Click "Finish"
• Accept the restart.
• Notice the presence of the releng tools (should be listed in the installed software page)

Uninstall the releng tools from End User UI

• Help>Software Updates
  • Go to Installed features page
  • Check mark the releng tools
  • Uninstall
• Accept the restart
• Come back up and notice the absence of the releng tools (no longer listed in installed software page)

Update the SDK

• Ensure you are connected to a site with a newer version of the SDK
• Help>Software Updates
• First verify that the Available Features page has an updated SDK
  • Choose "Add site..." and add the test site if you need to
• Now go to Installed features page
  • Click "Updates..."
  • You should see the new SDK offered as an update.
  • You shouldn't have to accept a license (assuming the EPL is the same for the updated SDK as it was for releng tools)
  • Finish the wizard, accept the restart when done
  • Verify that the Installed Software page now shows the new version

Reverting the configuration

• Go to the installed software page
• Choose "Revert Configuration..." and select a timestamped configuration that does not have the upgrade that you just did
• Push Finish and restart
• In the installed software list, verify that the original SDK version is there

Automatic updates (part 1)

• After restarting from the previous test...
  • User Group A - you should get the popup telling you that software updates were found (for the upgrade you just reverted from). Click to close the popup so that you get reminded again later.
  • User Group B - you should a popup at the specified time telling you the update was downloaded. Close the popup.
  • User Group C = you should not get any automatic update notifications

Automatic updates (part 2) User Group A & B

• User group A & B should see an affordance in the status bar for the updates that are available. (It appears

once you've been reminded about updates).

• Click on the status bar
• You should see the update wizard containing the SDK update

Automatic updates (part 2) User Group C

• Go to Installed features page
• Click "Check for Updates"
• You should get an update wizard showing the SDK update

Update (part 3), all users

• You should be looking at an update wizard with the SDK update
• Select the IU and you should see the update description in the details area of the wizard
• If you uncheck the IU, you should get an error message
• Check it again, and you'll see a progress bar while the validity is being computed
• You should not have to visit the license page since you have already done this upgrade
• Go ahead and update
• The affordance should be gone and there should be no more reminding of updates.

Sanity checking of the repositories

• Try adding different sites #Test Sites in different ways.
  • Drag URL's from browsers to different targets
    • Available software page
    • Repository dialog (Manage sites...)
    • Add site dialog entry field
  • Drag folders from platform browsers to same targets (may not work on Mac and Unix, please annotate https://bugs.eclipse.org/bugs/show_bug.cgi?id=223991 with your findings)
  • Use the archive button in the add site dialog to add a jar or zip
  • Use the local button in the add site dialog to add a folder
• Use the manage sites dialog to disable some sites
  • Verify that the content of disabled sites is no longer showing

Import/export of repositories from UM

• Start up an Eclipse 3.3 install and export the repositories from update manager
  • Help>Software Updates>Find and Install...
  • Search for new features to Install>Next...
  • In the "Update sites to visit" list, note what sites are there and whether they are checked or not
  • Export...
• In your M7 test SDK...
  • Help>Software Updates
  • Available Software>Manage Sites...
  • Import...
  • Select the file you just exported
  • You should see the same sites appear with the same check marks. The old site names will not be remembered, this is a known limitation.
  • Browse the content of the new repositories to sanity check that you are seeing what you expect

Import/export from p2

• • Help>Software Updates
  • Available Software>Manage Sites...
  • Export... to a file
  • Select all of the repos and remove them with the remove sites...button
  • Import... from the file you just exported
  • Everything should be restored as you expect

General preferences

• Go to the Install/Update preferences
• Click the "Show all versions of available software" button and close the prefs
• Help>Software Updates
  • Go to the installed features page and check for updates
  • You should see every version of the SDK that is newer than what you installed, not just the latest
  • The latest one should be checked in the wizard
  • Try checking other ones or combinations and see what the resolver does

Connection to authenticated sites

• This test requires access to a repository that requires authenticated login
• Click "Add Site", and add the new repository
• Attempt to expand the site to see the contents, and you should be prompted for login
• You will get three attempts to provide a valid username and password
• If you enter three bad passwords, you need to remove and re-add the repository to be able to try again, or restart Eclipse
• After entering a valid password, shutdown and restart to verify that the password is correctly persisted across sessions

Signature trust check during install

• Connect to a repository that contains self-signed features, or features signed with a certificate that is not already linked to a certificate in your trust store.
  • Need better directions here - sample site and how to clean out the trust store
• Attempt to install software that contains software of unknown trust
• Dialog opens showing certificate chain
• Should be able to look at details of each certificate in a separate dialog
• Close the dialog without indicating that you trust any certificates
• Install should abort, but content will remain downloaded in your eclipse/plugins directory
• Attempt to install the same software again
• Nothing will be downloaded, but you will be asked again to establish trust
• Indicate that you trust the certificate provider
• Install should succeed
• Uninstall the software
• Shutdown and restart
• Attempt to install the software again, and you should not be prompted again to establish trust (broken in 3.4 M7)