From Fedora Project Wiki
(Relval bot-created Desktop validation results page for Fedora 32 Branched 20200401.n.1) |
|||
| (18 intermediate revisions by 3 users not shown) | |||
| Line 12: | Line 12: | ||
| Basic | | Basic | ||
| [[QA:Testcase_desktop_browser]] | | [[QA:Testcase_desktop_browser]] | ||
| {{result| | | {{result|pass|coconut|bot=true}}{{result|pass|lruzicka}} | ||
| {{result| | | {{result|pass|coconut|bot=true}} | ||
|- | |- | ||
| Basic | | Basic | ||
| [[QA:Testcase_desktop_app_basic]] - terminal emulator | | [[QA:Testcase_desktop_app_basic]] - terminal emulator | ||
| {{result| | | {{result|pass|lruzicka}} | ||
| {{result|none}} | | {{result|none}} | ||
|- | |- | ||
| Beta | | Beta | ||
| [[QA:Testcase_desktop_login]] | | [[QA:Testcase_desktop_login]] | ||
| {{result| | | {{result|pass|lruzicka}} | ||
| {{result|none}} | | {{result|none}} | ||
|- | |- | ||
| Beta | | Beta | ||
| [[QA:Testcase_audio_basic]] | | [[QA:Testcase_audio_basic]] | ||
| {{result| | | {{result|pass|lruzicka}} | ||
| {{result|none}} | | {{result|none}} | ||
|- | |- | ||
| Beta | | Beta | ||
| [[QA:Testcase_desktop_panel_basic]] | | [[QA:Testcase_desktop_panel_basic]] | ||
| {{result| | | {{result|lruzicka}} | ||
| {{result|none}} | | {{result|none}} | ||
|- | |- | ||
| Line 42: | Line 42: | ||
| Beta | | Beta | ||
| [[QA:Testcase_workstation_core_applications]] | | [[QA:Testcase_workstation_core_applications]] | ||
| {{result| | | {{result|pass|coconut|bot=true}} | ||
| style="background:lightgrey;"| | | style="background:lightgrey;"| | ||
|- | |- | ||
| Beta | | Beta | ||
| [[QA:Testcase_desktop_update_graphical]] | | [[QA:Testcase_desktop_update_graphical]] | ||
| {{result| | | {{result|pass|coconut|bot=true}} | ||
| {{result| | | {{result|pass|coconut|bot=true}} | ||
|- | |- | ||
| Beta | | Beta | ||
| [[QA:Testcase_Printing_New_Printer]] - real printer | | [[QA:Testcase_Printing_New_Printer]] - real printer | ||
| {{result| | | {{result|pass|lruzicka}} | ||
| {{result|none}} | | {{result|none}} | ||
|- | |- | ||
| Beta | | Beta | ||
| [[QA:Testcase_Printing_New_Printer]] - virtual printer | | [[QA:Testcase_Printing_New_Printer]] - virtual printer | ||
| {{result| | | {{result|pass|lruzicka}} | ||
| {{result|none}} | | {{result|none}} | ||
|- | |- | ||
| Line 63: | Line 63: | ||
| [[QA:Testcase_desktop_update_notification]] | | [[QA:Testcase_desktop_update_notification]] | ||
| {{result|none}} | | {{result|none}} | ||
| {{result| | | {{result|pass|coconut|bot=true}} | ||
|- | |- | ||
| Final | | Final | ||
| [[QA:Testcase_desktop_error_checks]] | | [[QA:Testcase_desktop_error_checks]] | ||
| {{result|none}} | | {{result|none}} | ||
| {{result| | | {{result|pass|coconut|bot=true}} | ||
|- | |- | ||
| Final | | Final | ||
| Line 82: | Line 82: | ||
| Final | | Final | ||
| [[QA:Testcase_desktop_app_basic]] - file manager | | [[QA:Testcase_desktop_app_basic]] - file manager | ||
| {{result| | | {{result|pass|lruzicka}}<ref>The behaviour of the GTK FileDialog is illogical, but apparently, it is a feature.</ref> | ||
| {{result|none}} | | {{result|none}} | ||
|- | |- | ||
| Line 97: | Line 97: | ||
| Final | | Final | ||
| [[QA:Testcase_desktop_app_basic]] - document viewer | | [[QA:Testcase_desktop_app_basic]] - document viewer | ||
| {{result| | | {{result|pass|lruzicka}}<ref>Night mode does not work correctly - https://gitlab.gnome.org/GNOME/evince/-/issues/1334</ref> | ||
| {{result|none}} | | {{result|none}} | ||
|- | |- | ||
| Final | | Final | ||
| [[QA:Testcase_desktop_app_basic]] - text editor | | [[QA:Testcase_desktop_app_basic]] - text editor | ||
| {{result| | | {{result|pass|lruzicka}} | ||
| {{result|none}} | | {{result|none}} | ||
|- | |- | ||
| Line 117: | Line 117: | ||
| Final | | Final | ||
| [[QA:Testcase_desktop_app_basic]] - help viewer | | [[QA:Testcase_desktop_app_basic]] - help viewer | ||
| {{result| | | {{result|pass|lruzicka}} | ||
| {{result|none}} | | {{result|none}} | ||
|- | |- | ||
| Final | | Final | ||
| [[QA:Testcase_desktop_app_basic]] - system settings | | [[QA:Testcase_desktop_app_basic]] - system settings | ||
| {{result| | | {{result|pass|lruzicka}} | ||
| {{result|none}} | | {{result|none}} | ||
|- | |- | ||
| Line 268: | Line 268: | ||
| {{result|none}} | | {{result|none}} | ||
| {{result|none}} | | {{result|none}} | ||
| {{result| | | {{result|pass|coconut|bot=true}} | ||
|- | |- | ||
| Basic | | Basic | ||
Latest revision as of 09:50, 3 April 2020
No longer current
The compose for which this page contains results is no longer the current one. This page contains the results for the current compose.
The compose for which this page contains results is no longer the current one. This page contains the results for the current compose.
This page records Desktop validation testing test results for the Fedora 32 20200401.n.1 nightly compose.
Which tests to run[edit]
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.
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 Basic, 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 Basic 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.
How to test[edit]
1. Download one or more media for testing:
| Image | aarch64 | armhfp | ppc64le | s390x | x86_64 |
|---|---|---|---|---|---|
| Everything boot | Download | Download | Download | Download | |
| Workstation live | Download | Download | |||
| Server dvd | Download | Download | Download | Download | Download |
| Server boot | Download | Download | Download | Download | Download |
| Cloud_Base qcow2 | Download | Download | Download | ||
| Cloud_Base raw-xz | Download | Download | Download | ||
| Cloud_Base vmdk | Download | Download | Download | ||
| Cloud_Base vagrant-libvirt | Download | ||||
| Cloud_Base vagrant-virtualbox | Download | ||||
| KDE live | Download | ||||
| Xfce live | Download | ||||
| SoaS live | Download | ||||
| Mate live | Download | ||||
| Cinnamon live | Download | ||||
| LXDE live | Download | ||||
| Container_Base docker | Download | Download | Download | ||
| Container_Minimal_Base docker | Download | Download | Download | ||
| Python_Classroom vagrant-libvirt | Download | ||||
| Python_Classroom vagrant-virtualbox | Download | ||||
| Astronomy_KDE live | Download | ||||
| Comp_Neuro live | Download | ||||
| Design_suite live | Download | ||||
| Games live | Download | ||||
| Jam_KDE live | Download | ||||
| Python_Classroom live | Download | ||||
| Security live | Download | ||||
| Silverblue dvd-ostree | Download | Download | Download | ||
| LXQt live | Download | ||||
| Workstation raw-xz | Download | Download | |||
| Server raw-xz | Download | Download | |||
| KDE raw-xz | Download | ||||
| Minimal raw-xz | Download | Download | |||
| Xfce raw-xz | Download | Download | |||
| SoaS raw-xz | Download | ||||
| Mate raw-xz | Download | ||||
| LXDE raw-xz | Download | ||||
| Python_Classroom raw-xz | Download | ||||
| LXQt raw-xz | 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-resultscommand. 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.
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.
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.
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.
Virtual machine testing
In most cases, testing in a virtual machine is OK. You can test UEFI (including SecureBoot) in VMs as well.
In most cases, testing in a virtual machine is OK. You can test UEFI (including SecureBoot) in VMs as well.
Results summary page[edit]
The Test Results:Fedora 32 Branched 20200401.n.1 Summary page contains the results from this page and all the other validation pages for the same compose listed together to provide an overview.
Add, Modify or Remove a Test Case[edit]
- 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).
- Once reviewed, make your changes to any current documents that use the template (e.g. Test_Results:Current_Desktop_Test).
- Lastly, update Template:Desktop_test_matrix with the same changes.
Key[edit]
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 |
|---|---|---|
| Untested - This test has not been run, and is available for anyone to contribute feedback. | {{result|none}}
| |
 robatino |
Passed - The test has been run and the tester determine the test met the expected results | {{result|pass|robatino}}
|
| 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}}
| |
| Failed - Indicates a failed test. A link to a bug must be provided. See Template:Result for details on providing bug information. | {{result|fail|jlaska|XYZ|ZXY}}
| |
| [1] | Warning - This test completed and met the expected results of the test, but other issues were encountered during testing that warrant attention.
|
{{result|warn|rhe}} <ref>Brief description about the warning status</ref>
|
| Multiple results - More people can easily provide results to a single test case. | {{result|pass|hongqing}} {{result|warn|kparal}}
| |
| Failed - Same issue with LVM again | {{result|fail|pboy|2246871|2244305}}
| |
| 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 Matrix[edit]
Release-blocking desktops: x86 / x86_64[edit]
- ↑ The behaviour of the GTK FileDialog is illogical, but apparently, it is a feature.
- ↑ Night mode does not work correctly - https://gitlab.gnome.org/GNOME/evince/-/issues/1334
Release-blocking desktops: ARM[edit]
Non release-blocking desktops: x86 / x86_64[edit]
Non release-blocking desktops: ARM[edit]
Sugar (non-blocking, all arches)[edit]
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.
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 | ||
| QA:Testcase_SoaS installed to hard disk with liveinst from root terminal | ||
| QA:Testcase_Jabber.sugarlabs.org should connect and display XO "Buddies" | ||
| QA:Testcase_When a USB storage device is inserted, it should show up in the Frame | ||
| QA:Testcase_Functions in My Settings (Sugar control panel) | ||
| QA:Testcase_Applications in the Home Screen | ||
| QA:Testcase_Sugar-desktop installed in another Desktop |