From Fedora Project Wiki

(Test Results: add template from satellit)
m (Test Results)
Line 54: Line 54:
 
== Test Results ==
 
== Test Results ==
  
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=13&component=sugar component].  Issues with Sugar activities which do not appear to be Fedora-specific should be filed in the [http://bugs.sugarlabs.org/ Sugarlabs bug tracker].  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 [[Template:result|result template]] to enter your result, as shown in the example result line.
+
If you have problems with any of the tests, report a bug to [https://bugzilla.redhat.com Bugzilla] usually for the [https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&version=17&component=sugar component].  Issues with Sugar activities which do not appear to be Fedora-specific should be filed in the [http://bugs.sugarlabs.org/ Sugarlabs bug tracker].  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 [[Template:result|result template]] to enter your result, as shown in the example result line.
  
 
{| class="wikitable collapsible" border="0" width="85%"
 
{| class="wikitable collapsible" border="0" width="85%"
Line 122: Line 122:
 
|}
 
|}
 
|}
 
|}
+
 
 
== USB Stick ==
 
== USB Stick ==
 
{| class="wikitable collapsible" border="1" width="85%"
 
{| class="wikitable collapsible" border="1" width="85%"

Revision as of 00:43, 22 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 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 ...

Prerequisite for Test Day

The following prerequisites are recommended:

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

Test Results

If you have problems with any of the tests, report a bug to Bugzilla usually for the component. Issues with Sugar activities which do not appear to be Fedora-specific should be filed in the Sugarlabs bug tracker. 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.

Test Results Format
Test Result Explanation Code Entered
none
Untested - This test has not been run, and is available for anyone to contribute feedback. {{result|none}}
Pass pass robatino
Passed - The test has been run and the tester determine the test met the expected results {{result|pass|robatino}}
Inprogress inprogress adamwill
Inprogress - An inprogress result is often used for tests that take a long time to execute. Inprogress results should be temporary and change to pass, fail or warn. {{result|inprogress|adamwill}}
Fail fail jlaska [1] [2]
Failed - Indicates a failed test. A link to a bug must be provided. See Template:Result for details on providing bug information.
  1. RHBZ #XYZ
  2. RHBZ #ZXY
{{result|fail|jlaska|XYZ|ZXY}}
Warning warn rhe
[1]
Warning - This test completed and met the expected results of the test, but other issues were encountered during testing that warrant attention.
  1. Brief description about the warning status
{{result|warn|rhe}} <ref>Brief description about the warning status</ref>
Pass pass hongqing
Warning warn kparal
Multiple results - More people can easily provide results to a single test case. {{result|pass|hongqing}} {{result|warn|kparal}}
Pass pass previous <build> run
Result from previous test run - This test result is directly moved from the test run of previous <build>. {{result|pass|previous <build> run}}
none
Unsupported - An unsupported test or configuration. No testing is required.

Live Image

Live.iso installation
Release Level Test Area Test Case i386 x86_64
Alpha/Final Image Sanity QA:Testcase_Mediakit_ISO_Checksums
none
none
Alpha Boot Methods QA:Testcase_Live_Image_Boot
none
none

USB Stick

USB installation
Release Level Test Area Test Case i386 x86_64
Alpha Boot Methods QA:Testcase_USB_stick_Live Live-ISO-to-Disk
none
none
Alpha Boot Methods QA:Testcase_USB_stick_Live LiveCD-tools
none
none
Alpha Boot Methods QA:Testcase_USB_stick_Live_dd
none
none