[[PageOutline]] = Testing Changes = Before packages can move from the `-development` repository to the `-proposed` repository, they must undergo testing. There are two types of tests: functionality tests and package-specific tests. Functionality tests include, e.g., printing. Whenever any package is changed that impacts printing (cupsys-config, printing-config), the printing functionality test must be performed. Skipping a test or test component requires explicit approval of three (3) members of release-team. Package-specific tests are listed by the name of the package. == Printing == The Debathena printing configuration is sufficiently complicated and contains enough points of failure that it requires a sigificant amount of testing before we deem that changes involving printing can be pushed to production. === GTK+-based printing applications, including evince === From at least two (2) GTK+-based applications, one of which is evince, test the following: * Verify picklist is complete * Printing simplex from the picklist * Printing duplex from the picklist * Printing simplex with "Print to LPR" * Printing duplex with "Print to LPR" * Print simplex or duplex in color === Java-based printing applications, including MATLAB and OpenOffice === From at least 3 Java-based printing applications (which must include MATLAB and OpenOffice): * Verify picklist/dropdown is complete * Print simplex * Print duplex * Print simplex or duplex in color === Command-line printing === * Print simplex * Print duplex == 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 is disabled.