wiki:TestPlan

Version 7 (modified by jdreed, 11 years ago) (diff)

--

Testing Changes

Before packages can move from the -development repository to the -proposed repository, they must undergo testing. Skipping a test or test component requires explicit approval of three (3) members of release-team.

Update Testing

A package must be successfully installed by the auto-updater on both debathena-workstation and debathena-cluster, unless the change affects a cluster-only package, in which case only debathena-cluster testing is necessary. The auto-updater may be invoked by hand (e.g. from recovery-mode), but ensure it runs outside the chroot on cluster machines. After a successful automatic update of the package, you must perform aptitude --simulate --assume-yes full-upgrade and ensure that no further updates are necessary.

Maintainer scripts

If any maintainer scripts (postinst, etc) are changed, a fresh installation must also be tested.

Package-specific test plans

gdm-config

Verify that it displays properly in the following resolutions:

  • 800x600
  • 1024x768
  • 1152x865
  • 1280x1024
  • 1680x1050

auto-update

Verify that auto-update is successfully invoked by cron.

cluster-login-config

  • Verify that user switching (including "Guest Session") is disabled or nonfunctional from the "power button" menu (indicator-applet-session) and the GNOME "Log Out" panel button.
  • Verify that VTs 1-6 have some sort of message encouraging users to switch back to X
  • Verify that root cannot log in to a graphical session
  • Verify that sshd is not running
  • Verify that the gnome-screensaver permits a force logout after 20 minutes of inactivity and that the logout function works
  • Verify that gnome-screensaver does not permit user-switching
  • Verify that the user cannot hibernate or suspend the machine (from indicator-applet-session or power-manager?)
  • Verify that the default window manager is Metacity (until #354 is fixed)
  • Verify that users can sudo.
  • Verify that the root password is correctly set.

reactivate

  • Verify that login sessions end up inside a chroot

kiosk

  • Verify that a browser can be started
  • Verify that the registration applet works and can connect to the moira server (this requires accepting the rules of use and getting to the point where it prompts for name and MIT ID number)

xsession

  • Verify that the Failsafe GNOME and Failsafe Terminal sessions are no longer displayed
  • Verify that there is a "Login without customizations" session Verify that it works Verify that selecting that session does not persist across logins

help-config

  • Verify that the Help panel icon correctly launches the Debathena help front page

metrics

  • Verify that metrics are being collected reported properly (requires coordination with ops or temporary change of syslog.conf)

locker-menu

  • Verify that each of the menu items successfully launches the application in question

thirdparty

  • Verify that it installs correctly on both amd64 and i386 on all supported releases

cupsys-config