Test Results:Fedora 22 Final RC1 Desktop

From FedoraProject

Jump to: navigation, search

This page records Desktop validation testing test results for the Fedora 22 Final RC1 compose.

Contents

[edit] Which tests to run

Note.png
Test coverage page
This page provides information about test coverage for the tests on this page across all the composes for the current release: it can help you see which test cases most need to be run.

Tests with a Milestone of Alpha, Beta or Final are the most important. Optional tests are less so, but still useful to run. The milestone indicates that for that milestone release or a later one to be approved for release, the test must have been run against the release candidate build (so at Beta, all Alpha and Beta tests must have been run, for instance). However, it is important to run the tests for all milestones as early and often as possible. Please refer to the test coverage page linked above and try to find and run tests which have not been run at all, or not run recently, for the current release.

[edit] How to test

1. Download one or more media for testing:

Image armhfp i386 x86_64
workstation netinst Download Download
workstation boot Download Download
workstation live Download Download
server netinst Download Download
server dvd Download Download
server boot Download Download
cloud boot Download DownloadDownload
cloud Download
cloud base disk DownloadDownload DownloadDownload
cloud atomic disk DownloadDownload
cloud netinst Download Download
kde live Download Download
xfce live Download Download
soas live Download Download
mate live Download Download
lxde live Download Download
games live Download Download
scientific_kde live Download Download
jam_kde live Download Download
design_suite live Download Download
robotics live Download Download
security live Download Download
workstation disk Download
server disk Download
kde disk Download
xfce disk Download
soas disk Download
mate disk Download
lxde disk Download

2. Perform one or more of the test cases and add your results to the table below

  • You can submit results by editing the page directly, or by using relval, with the relval report-results command. It provides a simple text interface for reporting test results.

3. If a test fails, file a bug report. You may propose the bug as a release blocker or freeze exception bug for the appropriate release - see blocker bug process and freeze exception bug process.

Some tests must be run against particular Products or images - for example, the #Default boot and install tests. If no particular product or image is specified either in this page or the test case page, you can use any appropriate image. For example, you can run most of the #General Tests with the Workstation live image, or either of the Server install images.

Delta_ISOs for Server offline installer images are available here. If you have the Server offline install image for the previous TC/RC (or in the case of Alpha TC1, the previous stable release), you can generate the current install image with greatly reduced download size.

If you notice a problem during a test which does not constitute a complete failure of the test, you should still file a bug report, but it may not be appropriate to propose it as a release blocker bug. Use your judgment in deciding this, with reference to the Fedora_Release_Criteria, which these tests are intended to verify. If you are unsure, err on the side of proposing the bug as a blocker.

Important.png
Don't install updates
Don't install updates before performing any of the tests, as when you are testing pre-releases, available updates are not part of the proposed released package set.
Note.png
Virtual machine testing
In most cases, testing in a virtual machine is OK. You can test UEFI (including SecureBoot) in VMs as well.

[edit] Results summary page

The Test Results:Fedora 22 Final RC1 Summary page contains the results from this page and all the other validation pages for the same compose listed together to provide an overview.

[edit] Add, Modify or Remove a Test Case

  1. Please request review for your changes by publishing your test case for review to the test mailing list and/or the appropriate working group mailing list (e.g. server, cloud, or desktop).
  2. Once reviewed, make your changes to any current documents that use the template (e.g. Test_Results:Current_Desktop_Test).
  3. Lastly, update Template:Desktop_test_matrix with the same changes.

[edit] Key

See the table below for a sample format for test results. All test results are posted using the result template.


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.

[edit] Test Matrix

[edit] Release-blocking desktops: x86 / x86_64

Milestone Test Case Workstation KDE
Alpha QA:Testcase_desktop_browser
none
none
Alpha QA:Testcase_desktop_terminal
none
none
Beta QA:Testcase_desktop_update_graphical
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_workstation_core_applications
none
Final QA:Testcase_desktop_update_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
Optional QA:Testcase_workstation_theming
none


[edit] Release-blocking desktops: ARM

Milestone Test Case KDE
Alpha QA:Testcase_desktop_browser
none
Alpha QA:Testcase_desktop_terminal
none
Beta QA:Testcase_desktop_update_graphical
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
Final QA:Testcase_desktop_update_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


[edit] Non release-blocking desktops: x86 / x86_64

Milestone Test Case Xfce LXDE MATE Cinnamon GNOME Classic
Alpha QA:Testcase_desktop_browser
none
none
none
none
none
Alpha QA:Testcase_desktop_terminal
none
none
none
none
none
Beta QA:Testcase_desktop_update_graphical
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
Final QA:Testcase_desktop_update_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


[edit] Non release-blocking desktops: ARM

Milestone Test Case Workstation Xfce LXDE MATE Cinnamon GNOME Classic
Alpha QA:Testcase_desktop_browser
none
none
none
none
none
none
Alpha QA:Testcase_desktop_terminal
none
none
none
none
none
none
Beta QA:Testcase_desktop_update_graphical
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_workstation_core_applications
none
Final QA:Testcase_desktop_update_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
Optional QA:Testcase_workstation_theming
none


[edit] Sugar (non-blocking, all arches)

Note.png
Sugar test cases
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
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