From Fedora Project Wiki

(Initial content.)
 
Line 57: Line 57:
== Test Cases ==
== Test Cases ==


Provide a list of test areas or test cases that you'd like contributors to execute.  For other examples, see [[:Category:Test_Cases]].
* [[QA:Testcase_Printing_New_Printer|Connecting a local printer]]: Expected behavior is that when a new local printer is connected, drivers will be installed as needed, a queue will be created for it, and the user will see a notification message about it.  '''Note that automatic installation of drivers is not yet implemented in GNOME Shell.'''
* [[QA:Testcase_Printing_Known_Printer|Reconnecting a local printer]]
* [[QA:Testcase_Printing_Network_Printer|Printing to a network printer]]
* [[QA:Testcase_Printing_Complex|Printing copies/pages/duplexing from the print dialog]]
* [[QA:Testcase_Printing_Troubleshooting|Error notification]]


== Test Results ==
== Test Results ==

Revision as of 15:38, 22 March 2011

Fedora Test Days
Echo-testing-48px.png
Printing

Date 2011-03-29
Time all day

Website QA/Fedora_15_test_days
IRC #fedora-test-day (webirc)
Mailing list test


Note.png
Can't make the date?
If you come to this page before or after the test day is completed, your testing is still valuable, and you can use the information on this page to test, file any bugs you find at Bugzilla, and add your results to the results section. If this page is more than a month old when you arrive here, please check the current schedule and see if a similar but more recent Test Day is planned or has already happened.

What to test?

Today's instalment of Fedora Test Day will focus on Printing.

There are several parts to this, and in Fedora 15 the situation is slightly more complicated due to developments in GNOME 3.

In previous Fedora releases the application used in GNOME for configuring printers was system-config-printer. In GNOME 3 parts of that application are being replaced by more tightly-integrated functionality in GNOME itself:

  • print job notifications are now implemented in gnome-settings-daemon
  • status feedback is expected to be implemented there soon as well
  • a new control center module for printing has been implemented

This test day is for testing all aspects of printing, including setting up the printer, sharing printers on the network, and printing jobs.

If you see a problem and are not sure which component is to blame, the Debugging Printing page can help you to diagnose it.

Who's available

The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...

Prerequisite for Test Day

How to test?

A variety of printing tasks should be attempted, including:

  • Configuring a printer not yet known to the system
  • Printing a test page
  • Printing something more complicated, e.g. OpenOffice document, PDF, email
  • Taking advantage of extra print features of your printer e.g. duplexing, stapling

Update your machine

If you're running Fedora 15 Alpha, make sure you have all the current updates for it installed, using the update manager. Or:

Live image

Optionally, you may download a non-destructive Rawhide live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here.

Test Cases

Test Results

If you have problems with any of the tests, report a bug to Bugzilla. Choose the correct component:

  • gnome-settings-daemon for problems relating to job reporting and printer status feedback in GNOME Shell
  • gnome-control-center for problems specific to printer administration in GNOME Shell e.g. the new system settings module
  • cups for printing problems that persist even when using command line utilities such as lp
  • gtk2 for printing problems common to all GTK+ applications using the GTK+ print dialog
  • system-config-printer for bugs in the printing configuration program used in GNOME fallback mode and in other graphical environments

If you are unsure about exactly how to file the report or what other information to include, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below, following the example results from the first line as a template. The first column should be your name with a link to your User page in the Wiki if you have one, and the second should be a link to the Smolt profile of the system you tested. For each test case, use the result template to enter your result, as shown in the example result line.

User Smolt Profile Sample test 1 Sample test 2 Sample test 3 Sample test 4 References
Sample User HW
none
Pass pass
Warning warn
[1]
Fail fail
[2]
  1. Test pass, but also encountered RHBZ #54321
  2. RHBZ #12345