Test Day:2010-08-19 Sugar

From FedoraProject

Revision as of 13:42, 5 April 2011 by Jlaska (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Warning (medium size).png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page. This page is a draft and is not final.
DATE TIME WHERE
2010-08-19 From 12:00 to 21:00 UTC (8am -> 5pm EDT) #fedora-test-day (webirc)
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 - which should be linked at QA/Test_Days - and see if a similar but more recent Test Day is planned or has already happened.

Contents

[edit] What to test?

Today's installment of Fedora Test Day will focus on Sugar

[edit] Who's available

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

[edit] Prerequisite for Test Day

  • a USB Key (at least 2 GB)
  • link to updated snapshot goes here
  • your hardware profile uploaded to Smolt according to these instructions

[edit] How to test?

Follow the instructions provided in our Creation Kit, however, use the freshly built snapshot image listed above instead of Sugar on a Stick v3.

[edit] 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.

[edit] 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, if your system worked correctly, simply enter the word PASS. If you had trouble, enter the word FAIL, with a footnote indicator, and put a link to the bug report in the References column (as in the example line). For tests you could not perform, enter a dash.

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