From Fedora Project Wiki

m (Add browser result)
(automated category move, see https://lists.fedoraproject.org/pipermail/test/2014-October/123052.html)
 
(12 intermediate revisions by 3 users not shown)
Line 46: Line 46:
| Alpha
| Alpha
| [[QA:Testcase_desktop_browser]]
| [[QA:Testcase_desktop_browser]]
| {{result|pass|jlaska}}
| {{result|pass|jlaska}} {{result|pass|ivancjimenez}}
| <!--{{result|pass|kkofler}}KDE Live 20100328.17<br>(Konqueror, extension mechanism = konq-plugins)-->
| {{result|pass|jreznik}}
|  
|  
|  
|  
Line 54: Line 54:
| Alpha
| Alpha
| '''[[QA:Testcase_desktop_updates]]'''
| '''[[QA:Testcase_desktop_updates]]'''
| <!--{{result|warn|adamw}} <ref>Hits [https://bugzilla.redhat.com/show_bug.cgi?id=576423 Bug #576423] after updating complete, [https://bugzilla.redhat.com/show_bug.cgi?id=567346 Bug #567346] may also still be in play</ref>--> |
| {{result|pass|jlaska}} {{result|pass|ivancjimenez}} <!--{{result|warn|adamw}} <ref>Hits [https://bugzilla.redhat.com/show_bug.cgi?id=576423 Bug #576423] after updating complete, [https://bugzilla.redhat.com/show_bug.cgi?id=567346 Bug #567346] may also still be in play</ref>-->
| <!--{{result|warn|kkofler}}<ref>Found the same non-blocking glitches as in the current F12 updates: update types (security, bugfix, enhancement) are no longer distinguished, and there's a prompt for rebooting before the updates are installed (and a second, correct one after it's done).</ref><br>KDE Live 20100328.17<br>(KPackageKit)-->
| {{result|warn|jreznik}} <ref>With the same annoying glitches as Kevin Kofler observed in RC1.</ref>
|  
|  
|  
|  
Line 62: Line 62:
| Beta
| Beta
| [[QA:Testcase_audio_basic]]
| [[QA:Testcase_audio_basic]]
| <!--{{result|pass|adamw}}-->
| <!--{{result|pass|adamw}}--> {{result|fail|ivancjimenez|579272}}
|  
|  
|  
|  
Line 70: Line 70:
| Beta
| Beta
| [[QA:Testcase_desktop_panel_basic]]
| [[QA:Testcase_desktop_panel_basic]]
| <!--BetaRC1x86_64<br>Default Graphical Desktop {{result|pass|boblfoot}}2010-03-29-->
|{{result|pass|ivancjimenez}} <!--BetaRC1x86_64<br>Default Graphical Desktop {{result|pass|boblfoot}}2010-03-29-->
| <!--{{result|pass|adamw}}-->
| {{result|pass|jreznik}}
|  
|  
|  
|  
Line 78: Line 78:
| Beta
| Beta
| [[QA:Testcase_desktop_automount]]
| [[QA:Testcase_desktop_automount]]
| <!--{{result|pass|adamw}}-->
| <!--{{result|pass|adamw}}--> {{result|pass|ivancjimenez}}
|  
|  
|  
|  
Line 86: Line 86:
| Final
| Final
| [[QA:Testcase_desktop_error_checks]]
| [[QA:Testcase_desktop_error_checks]]
| <!--{{result|pass|adamw}}-->
|{{result|fail|ivancjimenez|578885|578888}}<ref>only tested live image</ref> <!--{{result|pass|adamw}}-->
|  
|  
|  
|  
Line 103: Line 103:
| [[QA:Testcase_desktop_panel_advanced]]
| [[QA:Testcase_desktop_panel_advanced]]
| <!--{{result|pass|adamw}}-->
| <!--{{result|pass|adamw}}-->
|  
| {{result|pass|jreznik}}
|  
|  
|  
|  
Line 111: Line 111:


[[Category:Fedora 13 Test Results]]
[[Category:Fedora 13 Test Results]]
[[Category: Fedora 13 Beta RC Test Results|D]]
[[Category: Fedora 13 Beta Test Results|D]]

Latest revision as of 20:27, 1 October 2014

This page records desktop validation testing test results for the Fedora 13 Beta RC3 release.

How to test[edit]

  1. Download the ISO images for testing -- Please use either the Live Desktop image or install using the default package set from the DVD installer image. Space is provided in the results matrix for recording tests on other desktops, but the results for the default desktop environment are most important. Delta ISOs for the DVD images are also available.
  2. Install, if appropriate (some tests may be intended to test the un-installed live environment).
  3. Perform one or more of the test cases and add your results to the table below.
Virtual machine testing
In most cases, testing in a virtual machine is OK.

Key[edit]

See the table below for a sample format for test results.

Test Result Explanation
none
Untested - This test has not been run, and is available for anyone to contribute feedback.
Pass pass liam
Passed - The test has been run and the tester determine the test met the expected results
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.
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
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
Pass pass rhe
Warning warn kparal
Multiple results - More people can easily provide results to a single test case.
none
Unsupported - An unsupported test or configuration. No testing is required.

Results Matrix[edit]

Release level Test Case Desktop KDE Xfce LXDE References
Alpha QA:Testcase_desktop_browser
Pass pass jlaska
Pass pass jreznik
Alpha QA:Testcase_desktop_updates
Pass pass jlaska
Warning warn jreznik
[1]
  1. With the same annoying glitches as Kevin Kofler observed in RC1.
Beta QA:Testcase_audio_basic
  1. RHBZ #579272
Beta QA:Testcase_desktop_panel_basic
Pass pass jreznik
Beta QA:Testcase_desktop_automount
Final QA:Testcase_desktop_error_checks [3]
  1. RHBZ #578885
  2. RHBZ #578888
  3. only tested live image
Final QA:Testcase_desktop_menus
Final QA:Testcase_desktop_panel_advanced
Pass pass jreznik