| Fedora Test Days | |
|---|---|
| |
| Sugar Desktop Test Day | |
| Date | 22 March 2012 |
| Time | 8:00-20:00 UTC |
| Website | QA/Fedora_17_test_days |
| IRC | #fedora-test-day (webirc) |
| Mailing list | test |
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 installment of Fedora Test Day will focus on the Sugar Desktop environment. Sugar is an alternative desktop environment meant to be educational & user-friendly for children.
More information about Sugar can be found at the Sugar Labs web site.
Who's available
The following cast of characters will be available testing, workarounds, bug fixes, and general discussion ...
- Development - Simon Schampijer (Erikos)
- Quality Assurance - Samuel Greenfeld (Cerlyn)
Prerequisite for Test Day
The following prerequisites are recommended:
- USB stick (to test Sugar on a Stick)
- An updated Fedora 17 pre-release, Rawhide (tips on installing Rawhide below), or a SoaS Fedora 17 TC2 or SoaS nightly live image
- Your hardware profile uploaded to Smolt according to these instructions
How to test?
Live image
If you do not wish to alter your computer's existing software, you may download a non-destructive live image for your architecture. Tips on using a live image are available at FedoraLiveCD. Live images can be found here for Fedora 17 TC2. The "SoaS" image is the one you want to download.
Test Cases
- Items in Category:LiveCD_Test_Cases (with the SoaS image)
- Exploratory testing of the activities found at QA:Testcase_sugar_activity_list
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.
| User | Smolt Profile | Sample test 1 | Sample test 2 | Sample test 3 | Sample test 4 | References |
|---|---|---|---|---|---|---|
| Sample User | HW |  |
 |
 |