Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Equinox/p2/UI Manual Tests

< Equinox‎ | p2
Revision as of 20:19, 8 December 2008 by Susan franklin.us.ibm.com (Talk | contribs) (→‎Test Pass)

Sanity Tests

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

Sanity Test of Installed Features

  • Help->Installation Information...
  • You should see one entry for the SDK
  • You can expand this to see the SDK's requirements
  • Selecting a top-level item in this list should enable the update and uninstall button.
  • If any lower level items are selected, the buttons should be gray

Sanity checking of the repositories

  • Help->Install New Software...
  • Add one p2 and one update manager site (see #Test Sites)
    • Drag URL from browsers to different targets
      • Available software list in first page of wizard
      • Add site dialog entry field
  • Use the manage sites dialog to disable one of the sites
    • Verify that the content of disabled sites is no longer showing

Sanity Test of Available Software wizard page

  • Help->Install New Software...
  • 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

Test Pass 3.5 M5

Areas of Emphasis

  • Expanding the nodes in your "Installation Information" should show you what other group IU's (roughly translates to features) are required by the things you have installed
  • Try installing content that will bring in other major functionality. In the install and update wizards, on the page that shows the resolution results, try expanding the top level nodes. You should see the other group IU's (roughly translates to features) that are required by the things you have installed
  • Updates for software that you already have installed should have a special icon in the "Available Software List"

Test Pass Groups

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.

  • 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
    • Available Software - view by category, [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 tiem platform is started, Download new updates automatically, Notify me once
    • Available Software - view by site, [ ] show only latest versions, [ ] Include items that have already been installed
  • User Group C -
    • Preferences
      • Automatic Updates - Auto updates off
    • 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
  • Simon, Windows XP, UI group B
  • DJ, Linux, UI group C
  • John, Vista, Windows XP, UI group A
  • Susan, Windows XP, UI group B,C

Manual Tests

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 >Install New Software
    • Switch to Available Software Page
    • Set the view mode and check boxes for your user group

Sanity Test of Installed Features

  • Help->Installation Information...
  • You should see one entry for the SDK
  • You can expand this to see the SDK's requirements
  • Selecting a top-level item in this list should enable the update and uninstall buttons
  • If any lower level items are selected, the buttons should be gray

Add the test updates site using drag

  • Help->Install New Software...
  • Drag this link to the available software page: http://download.eclipse.org/eclipse/updates/3.5-I-builds
  • 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 wizard 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

  • Check mark the releng tools in the Available Software list
  • The next button should enable
  • Review choices in the wizard
  • You should have a gray finish button because releng tools has a license
  • Click "Next" and accept 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

  • Help>Installation Information...
  • Select 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)

General preferences/install/upgrade scenario

  • Make sure you have this site in your list of sites:
  • Help>Install New Software
    • Install "Field_Assist_Example Feature" 1.0.0
    • Apply Changes
  • Go to the Install/Update preferences
  • Click the "Show all versions of available software" button and close the prefs
  • Help>Check for Updates...
    • You'll get a wizard suggesting you install "Field_Assist_Example Feature 2.0.0"
    • Pressing the "Back" button will show a list that also includes version 1.1.0 of the same feature
    • Try checking the other version instead
    • Press "Next" and it will resolve again
    • Press "Back" and try selecting both, then "Next"
    • You should get a resolve error
    • Select version 1.1.0 and finish the update.

Update the SDK

  • Ensure you are connected to a site with a newer version of the SDK
  • First verify that the Available Features page has an updated SDK
    • Help->Install New Software...
    • Choose "Add site..." and add the test site if you need to
  • Help>Check for Updates...
    • You should see the new SDK offered as an update. You should be able to expand the SDK and see what items underneath

it will be also be installed

    • You should also see the "Field_Assist_Example Feature 2.0.0" offered as an update
    • You shouldn't have to accept a license for the SDK (assuming the EPL is the same for the updated SDK as it was for releng tools)
    • You will have a new license for the field assist feature
    • Finish the wizard, accept the restart when done
    • Verify that the Installed Software page now shows the new version of your upgrades

Reverting the configuration

  • Help>Installation Information...
  • Choose "Revert..." to open the revert wizard
  • 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 and Field Assist 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

  • Help->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 and Field Assist update
  • Select the IU and you should see the update description in the details area of the wizard
  • Press the "Previous" button in the wizard and uncheck the IU
  • You shouldn't be able to continue
  • Check the IU and you should be able to continue again.
  • 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 wizard 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 test SDK...
    • Help>Install New 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>Install New 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

Refresh changed repository content

  • Help->Install New Software...
  • click Refresh
  • list should refresh (may show "Pending..." if you are in category or name view) and you'll see the refresh job progress in the status line

<This test will be fleshed out to include an actual repo that changes and needs refreshing>

Connection to authenticated sites

  • This test requires access to a repository that requires authenticated login
    • Need a public site to test this
  • 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 - public 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

Switch to Update Manager for install handlers

  • Add the site http://www.developer.com/img/2007/03/upd-install-site.xml
  • Check "Feature Feature 1.0.0" and press the install button
  • A message box should appear that informs you that the feature cannot be installed and offers to launch the update manager.
  • Press "Launch" and verify that the update manager is launched.
Retrieved from "https://wiki.eclipse.org/index.php?title=Equinox/p2/UI_Manual_Tests&oldid=131999"

Back to the top