Test Day:2013-04-04 Printing: Difference between revisions

Revision as of 12:06, 13 March 2013

Fedora Test Days

Printing

Date	2013-04-11
Time	all day

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

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.

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 ...

Development - Tim Waugh (twaugh)

Prerequisite for Test Day

A printer
An updated Fedora 19 pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image

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 19, make sure you have all the current updates for it installed, using the update manager. If you want to try Rawhide, see the instructions on the Rawhide page on the various ways in which you can install or update to Rawhide. 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

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.

Checking the Device ID is correctly listed
The hpijs, gutenprint-cups, foomatic-db-ppds and foomatic packages all contain tags that associate them with the Device IDs for the printers they support. If you are not given the opportunity to install one of these packages when your printer is supported by them, it may be that they do not list its Device ID correctly. You can check this by running /usr/share/system-config-printer/check-device-ids.py as root.

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
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	Printer	Connect local	Reconnect local	Network printing	Copies/pages/duplex	Status feedback	References
Sample User	HP LaserJet 5	none	none	pass	warn ^[1]	fail ^[2]	↑ Test pass, but also encountered RHBZ #54321 ↑ RHBZ #12345
User	Printer	Connect local	Reconnect local	Network printing	Copies/pages/duplex	Status feedback	References

[1] Test pass, but also encountered RHBZ #54321

[2] RHBZ #12345

[1]

[2]

@@ Line 14: / Line 14: @@
 == What to test? ==
-Today's instalment of Fedora Test Day will focus on '''Printing'''
+Today's instalment of Fedora Test Day will focus on '''Printing'''.
+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, [[Printing/Debugging|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 ...
-* Development - [[User:Developer1|Developer1]] (irc_nick1), [[User:Developer2|Developer2]] (irc_nick2)
+* Development - [[User:Twaugh|Tim Waugh]] (twaugh)
-* Quality Assurance - [[User:Tester1|Tester1]] (irc_nick3), [[User:Tester2|Tester2]] (irc_nick4), [[User:Tester3|Tester3]] (irc_nick5)
 == Prerequisite for Test Day ==
-List any prerequisite needs for the test event.  A fresh system, virtualized guest, a blank DVD ... a desire to break software?
+* A printer
-* Usb key
-* Usb externally connected HD IDE/SATA
-* Empty HD IDE/SATA/SCSI
-* Free space on HD
-Here's a chunk which is commonly used for most Test Days. Replace XX with whatever Fedora release is pending:
 * An updated [http://fedoraproject.org/get-prerelease Fedora 19 pre-release], [[Releases/Rawhide|Rawhide]] (tips on installing Rawhide below), or a [http://alt.fedoraproject.org/pub/alt/nightly-composes/desktop/ nightly live image]
 == How to test? ==
-High level details on how a contributor can get involved.  This can include (but not limited to):
+A variety of printing tasks should be attempted, including:
-* Areas to target with exploratory testing
-* A list of pre-defined test cases to execute
-* How to report back results
-Here's another common chunk (again, replace XX as above):
+* 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''' ===
@@ Line 55: / Line 49: @@
 == 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.
+{{admon/tip|Checking the Device ID is correctly listed|The hpijs, gutenprint-cups, foomatic-db-ppds and foomatic packages all contain tags that associate them with the Device IDs for the printers they support. If you are not given the opportunity to install one of these packages when your printer is supported by them, it may be that they do not list its Device ID correctly.  You can check this by running <code>/usr/share/system-config-printer/check-device-ids.py</code> as root.}}
+* [[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|Status feedback]]
 == Test Results ==
-Construct a table or list to allow testers to post results.  Each column should be a test case or configuration, and each row should consist of test results. Include some instructions on how to report bugs, and any special instructions. Here's an example, from a Palimpsest test day:
+If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla].  Choose the correct component:
-If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the component [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=udisks udisks], or [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=gnome-disk-utility gnome-disk-utility] for bugs in the Palimpsest graphical front end itself. 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. For each test case, use the [[Template:result|result template]] to enter your result, as shown in the example result line.
+* [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=19&component=gnome-settings-daemon gnome-settings-daemon] for problems relating to job reporting and printer status feedback in GNOME Shell
+* [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=19&component=control-center control-center] for problems specific to printer administration in GNOME Shell e.g. the new system settings module
+* [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=19&component=cups cups] for printing problems that persist even when using command line utilities such as '''lp'''
+* [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=19&component=gtk2 gtk2] for printing problems common to all GTK+ applications using the GTK+ print dialog
+* [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=19&component=system-config-printer 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 [[Template:result|result template]] to enter your result, as shown in the example result line.
 {|
 ! User
-! [[QA:Testcase_sample_1|Sample test 1]]
+! Printer
-! [[QA:Testcase_sample_2|Sample test 2]]
+! [[QA:Testcase_Printing_New_Printer|Connect local]]
-! [[QA:Testcase_sample_3|Sample test 3]]
+! [[QA:Testcase_Printing_Known_Printer|Reconnect local]]
-! [[QA:Testcase_sample_4|Sample test 4]]
+! [[QA:Testcase_Printing_Network_Printer|Network printing]]
+! [[QA:Testcase_Printing_Complex|Copies/pages/duplex]]
+! [[QA:Testcase_Printing_Troubleshooting|Status feedback]]
 ! References
 |-
 | [[User:SampleUser|Sample User]]
+| HP LaserJet 5
 | {{result|none}}
+| {{result|none}}
 | {{result|pass}}
 | {{result|warn}} <ref>Test pass, but also encountered {{bz|54321}}</ref>
@@ Line 78: / Line 87: @@
 | <references/>
 |-
+|-
+! User
+! Printer
+! [[QA:Testcase_Printing_New_Printer|Connect local]]
+! [[QA:Testcase_Printing_Known_Printer|Reconnect local]]
+! [[QA:Testcase_Printing_Network_Printer|Network printing]]
+! [[QA:Testcase_Printing_Complex|Copies/pages/duplex]]
+! [[QA:Testcase_Printing_Troubleshooting|Status feedback]]
+! References
 |}
 [[Category:Test Days]]
 [[Category:QA Templates]]

Search