TestingDLGReleases

DLG Testing Procedures

This page contains the testing procedures for DLG releases. It aims contains steps with what needs to be tested before making a public release and to ensure that all versions have the same quality standard.

Making sure all packages install cleanly

All packages should install cleanly when they are installed in the right order. In order to obtain the proper logs this has to be done without the installer.

• Download all packages
• Obtain the DroplineFilesX.XX file, where X.XX is the DLG Version to be tested

• Create a list of packages to be installed with the following command:

  cut -d: -f1 DroplineFilesX.XX > INSTALL_LIST

• Install all the packages with the bellow command:

  for PACKAGE in $(cat INSTALL_LIST)
  do
  upgradepkg --install-new "$PACKAGE" >> INSTALL_LOG 2>&1
  done

• Check the INSTALL_LOG file and look for errors/warning messages.

• If errors are found, make sure they were not already reported on trac. If they were not, fill out a new ticket.
• Reboot the system.

Checking system messages

• Check the boot messages to make sure no errors are appearing after the DLG installation.
• Start gnome manually on the console and check the log. Check all the errors, making sure there are none gnome-related.

GDM

• Create a few normal users and make sure they appear on the user list.
• Check if GNOME is the default session.
• Make sure there are also sessions for blackbox, enlightenment, fluxbox, fvwm2, gnome,kde, twm, windowmaker and xfce.
• Make sure that the desktop managers that are installed start without errors.
• Make sure that GDM is using the right theme.

Sound & Networking

Overall appearance

• Make sure that there is a wallpaper set.
• Make sure that the proper theme is installed.
• Make sure that the icons on the desktop+panel+menus are displayed correctly.

Step 5: Check the applets

• Make sure that all applets load properly by adding them to the panel (some might fail due to hardware limitations like the brightness applet. There is no need to test deprecated applets).

Applets that require special testing

• CPU Frequency Scaling Monitor:
  ** Try to change the cpu frequency and governors. It shouldn't ask for a password. If it does, it might be an issue with policykit.
• Clock: .
• Deskbar: .
• Time tracker: .
• Tomboy Notes: .

Step 5: Check Applications