From Fedora Project Wiki

m (moved Test Day:2012-03-22 to Test Day:2012-03-22 Sugar Desktop: Match naming scheme)
Line 4: Line 4:
 
| caption = Sugar Desktop Test Day
 
| caption = Sugar Desktop Test Day
 
| date = 22 March 2012
 
| date = 22 March 2012
| time = all day
+
| time = 8:00-20:00 UTC
 
| website = [[QA/Fedora_17_test_days]]
 
| website = [[QA/Fedora_17_test_days]]
 
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])
 
| irc = [irc://irc.freenode.net/#fedora-test-day #fedora-test-day] ([http://webchat.freenode.net/?channels=fedora-test-day webirc])

Revision as of 12:51, 20 March 2012

Fedora Test Days
Echo-testing-48px.png
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
MailSubscribeArchives


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

Prerequisite for Test Day

The following prequisites are recommended

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

Live image

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

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.

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