From Fedora Project Wiki

(add terminal test case to the matrix)
(add terminal test case some more)
Line 69: Line 69:
| Alpha
| Alpha
| [[QA:Testcase_desktop_browser]]
| [[QA:Testcase_desktop_browser]]
| {{result|none}}
| {{result|none}}
| <references/>
|-
| Alpha
| [[QA:Testcase_desktop_terminal]]
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
Line 209: Line 215:
| Alpha
| Alpha
| [[QA:Testcase_desktop_browser]]
| [[QA:Testcase_desktop_browser]]
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|-
| Alpha
| [[QA:Testcase_desktop_terminal]]
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
Line 315: Line 330:
| Alpha
| Alpha
| [[QA:Testcase_desktop_browser]]
| [[QA:Testcase_desktop_browser]]
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}
| <references/>
|-
| Alpha
| [[QA:Testcase_desktop_terminal]]
| {{result|none}}
| {{result|none}}
| {{result|none}}
| {{result|none}}

Revision as of 01:52, 15 March 2014

This page records desktop validation testing test results for the Fedora (VERSION) (PRE-RELEASE) release.

How to test

  1. Download the ISO images for testing: please use either the DVD installer image, or the nightly live image for the desktop you wish to test. Testing for all four major desktop environments is required for each test point. Delta_ISOs for installer images are also available here.
  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.
  4. If a test fails, file a bug report. If the bug is in the default desktop, propose the bug as a blocker for the appropriate release (see blocker bug process). If the bug is in any other desktop, propose it as a freeze exception bug for the appropriate release (see freeze exception bug process).
  5. Don't install updates before performing any of the tests, as the updates available come from updates-testing and are not part of the proposed released package set. For this reason, we recommend leaving the update installation test for last.
Virtual machine testing
In most cases, testing in a virtual machine is OK.

Add or Remove a Test Case

  1. Please request review for your changes by publishing your test case for review to test@lists.fedoraproject.org.
  2. Lastly, update QA:Desktop validation results template with the same changes.

Key

See the table below for a sample format for test results. All test results are posted using the format specified Template:Result.


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}}
Unsupported - An unsupported test or configuration. No testing is required.

Test Matrices

Release-blocking desktops: x86 / x86_64

Release Level Test Case Desktop (GNOME) KDE References
Alpha QA:Testcase_desktop_browser
none
none
Alpha QA:Testcase_desktop_terminal
none
none
Alpha QA:Testcase_desktop_updates (installation)
none
none
Beta QA:Testcase_desktop_login
none
none
Beta QA:Testcase_audio_basic
none
none
Beta QA:Testcase_desktop_panel_basic
none
none
Beta QA:Testcase_desktop_automount
none
none
Beta QA:Testcase_desktop_updates (notification)
none
none
Final QA:Testcase_desktop_error_checks
none
none
Final QA:Testcase_desktop_menus
none
none
Final QA:Testcase_desktop_panel_advanced
none
none
Final QA:Testcase_desktop_keyring
none
none

Release-blocking desktops: ARM

Release Level Test Case KDE References
Alpha QA:Testcase_desktop_browser
none
Alpha QA:Testcase_desktop_terminal
none
Alpha QA:Testcase_desktop_updates (installation)
none
Beta QA:Testcase_desktop_login
none
Beta QA:Testcase_audio_basic
none
Beta QA:Testcase_desktop_panel_basic
none
Beta QA:Testcase_desktop_automount
none
Beta QA:Testcase_desktop_updates (notification)
none
Final QA:Testcase_desktop_error_checks
none
Final QA:Testcase_desktop_menus
none
Final QA:Testcase_desktop_panel_advanced
none
Final QA:Testcase_desktop_keyring
none

Non release-blocking desktops: x86 / x86_64

Release Level Test Case Xfce LXDE MATE Cinnamon GNOME Classic References
Alpha QA:Testcase_desktop_browser
none
none
none
none
none
Alpha QA:Testcase_desktop_terminal
none
none
none
none
none
Alpha QA:Testcase_desktop_updates (installation)
none
none
none
none
none
Beta QA:Testcase_desktop_login
none
none
none
none
none
Beta QA:Testcase_audio_basic
none
none
none
none
none
Beta QA:Testcase_desktop_panel_basic
none
none
none
none
none
Beta QA:Testcase_desktop_automount
none
none
none
none
none
Beta QA:Testcase_desktop_updates (notification)
none
none
none
none
none
Final QA:Testcase_desktop_error_checks
none
none
none
none
none
Final QA:Testcase_desktop_menus
none
none
none
none
none
Final QA:Testcase_desktop_panel_advanced
none
none
none
none
none
Final QA:Testcase_desktop_keyring
none
none
none
none
none

Non release-blocking desktops: ARM

Release Level Test Case Desktop (GNOME) Xfce LXDE MATE Cinnamon GNOME Classic References
Alpha QA:Testcase_desktop_browser
none
none
none
none
none
none
Alpha QA:Testcase_desktop_terminal
none
none
none
none
none
none
Alpha QA:Testcase_desktop_updates (installation)
none
none
none
none
none
none
Beta QA:Testcase_desktop_login
none
none
none
none
none
none
Beta QA:Testcase_audio_basic
none
none
none
none
none
none
Beta QA:Testcase_desktop_panel_basic
none
none
none
none
none
none
Beta QA:Testcase_desktop_automount
none
none
none
none
none
none
Beta QA:Testcase_desktop_updates (notification)
none
none
none
none
none
none
Final QA:Testcase_desktop_error_checks
none
none
none
none
none
none
Final QA:Testcase_desktop_menus
none
none
none
none
none
none
Final QA:Testcase_desktop_panel_advanced
none
none
none
none
none
none
Final QA:Testcase_desktop_keyring
none
none
none
none
none
none

Sugar (non-blocking, all arches)

The Sugar desktop differs significantly from a typical desktop, so it gets its own test cases.

At present these live on the Sugar wiki.

Test Case x86 ARM References
QA:Testcase_SoaS boots to the (name) selection screen
none
none
QA:Testcase_SoaS installed to hard disk with liveinst from root terminal
none
none
QA:Testcase_Jabber.sugarlabs.org should connect and display XO "Buddies"
none
none
QA:Testcase_When a USB storage device is inserted, it should show up in the Frame
none
none
QA:Testcase_Functions in My Settings (Sugar control panel)
none
none
QA:Testcase_Applications in the Home Screen
none
none
QA:Testcase_Sugar-desktop installed in another Desktop
none
none