From Fedora Project Wiki

Which tests to run

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.

How to test

1. Download one or more media for testing:

Image ppc64 ppc64le
server netinst Alpah-RC6 Beta_TC2 Alpah-RC6 Beta_TC2
server dvd Alpha_RC6 Beta_TC2 Alpha_RC6 Beta_TC2
server boot
cloud dvd Beta_TC2 Beta_TC2
cloud netinst Beta_TC2 Beta_TC2
cloud boot

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 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.

Tracker bugs

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 Server install images.

For nightly compose testing, use the network install images linked above for Server tests. Cloud and non-Product live and disk images should be available from Koji via the searches linked above.|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.

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.
Virtual machine testing
In most cases, testing in a virtual machine is OK.

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.

Test Matrix

Server

Milestone Test Case PKVM BE PKVM LE PVM
Host Guest BE Guest LE Host Guest BE Guest LE LPAR BE LPAR LE
Alpha QA:Testcase_base_initial_setup
Alpha QA:Testcase_base_startup
none
Warning warn Alpha_RC6 menantea [1]
Warning warn Beta_TC2 menantea [1]
Warning warn Alpha_RC6 menantea
Warning warn Beta_TC2 menantea
[2]
Pass pass Beta_TC2 jcajka
[3]
Pass pass Alpha_RC6 efi
none
Alpha QA:Testcase_base_system_logging
none
Pass pass Alpha_RC6 menantea
Pass pass Beta_TC2 menantea
Pass pass Alpha_RC6 menantea
Pass pass Beta_TC2 jcajka
Pass pass Alpha_RC6 efi
none
Final QA:Testcase_Services_start
none
none
none
none
none
none
Final QA:Testcase_base_selinux
none
none
none
none
none
none
Final QA:Testcase_base_service_manipulation
none
none
none
none
none
none
  1. 1.0 1.1 RHBZ #1206060
  2. Background not colored as the one of ppc64 guest
  3. Bug https://bugzilla.linux.ibm.com/show_bug.cgi?id=122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU

Cloud

Milestone Test Case PKVM BE PKVM LE PVM
Host Guest BE Guest LE Host Guest BE Guest LE LPAR BE LPAR LE
Alpha QA:Testcase_base_initial_setup
Alpha QA:Testcase_base_startup
none
none
none
none
[1]
none
none
Alpha QA:Testcase_base_system_logging
none
none
none
none
none
none
Final QA:Testcase_Services_start
none
none
none
none
none
none
Final QA:Testcase_base_selinux
none
none
none
none
none
none
Final QA:Testcase_base_service_manipulation
none
none
none
none
none
none
  1. Bug https://bugzilla.linux.ibm.com/show_bug.cgi?id=122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU