From Fedora Project Wiki

Line 63: Line 63:
* [[QA:Testcase_Power_Management_personal]]
* [[QA:Testcase_Power_Management_personal]]
* [[QA:Testcase_Power_Management_Tuned]]
* [[QA:Testcase_Power_Management_bluetooth]]
* [[QA:Testcase_Power_Management_bluetooth]]
* [[QA:Testcase_Power_Management_init_1]]
* [[QA:Testcase_Power_Management_init_1]]

Revision as of 12:33, 1 April 2009

Thu April 02, 2009 From 12:00 to 00:00 UTC (7am -> 7pm ET) #fedora-qa)

What to test?

Today's instalment of Fedora Test Day will focus on:

Who's available

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

What's needed to test

Stop (medium size).png
Use caution
Remember, rawhide is a development branch. Use an installation you don't mind getting broken.

How to test?

Update your machine

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.

Architecture MD5SUM
i386 f5852f27e324fb87f4d060abf44d16dc
x86_64 195e48300a94c65289ffdb20d4eeb2d4

Latest syslinux package?
Creating a LiveUSB of this rawhide image requires the latest version of syslinux, which is currently available in Rawhide and in the latest Windows liveusb-creator. Users of F10 and below can upgrade to the latest syslinux package using
yum --enablerepo=rawhide update syslinux


Follow each of these test cases:

Report your results

During each of the tests for additional information please run the following script [1] as root. If you have problems with any of the tests, report a bug to Bugzilla. If you are unsure about exactly how to file the report, just ask on IRC and we will help you. Once you have completed the tests, add your results to the Results table below.

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 your Smolt hardware profile (see above for a link with instructions on submitting your hardware profile to Smolt). For each test case, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, as a link to the bug report for the failure. If you could not perform one test (for example, you cannot perform the more advanced tests because the basic one fails, or you cannot perform the multihead test as you have only one display), enter the word N/A. In case you ran the

script together with the tests copy & paste the output of the script to the corresponding column. In the comments column, enter any additional information that is related to your testing.


User Smolt Profile Personal Bluetooth Init 1 Bltk Comments