QA/Test Days/Template

What to test?
Today's instalment of Fedora Test Day will focus on <>

Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
 * Development - Developer1 (irc_nick1), Developer2 (irc_nick2)
 * Quality Assurance - Tester1 (irc_nick3), Tester2 (irc_nick4), 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?


 * 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 Fedora XX pre-release, Rawhide (tips on installing Rawhide below), or a nightly live image
 * Your hardware profile uploaded to Smolt according to these instructions

How to test?
High level details on how a contributor can get involved. This can include (but not limited to):


 * 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):

Update your machine
If you're running Fedora XX, 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
Provide a list of test areas or test cases that you'd like contributors to execute. For other examples, see Category:Test_Cases.

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 Bugzilla usually for the component udisks, or 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, 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.