Which tests to run
Test coverage pageThis 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
|
|
|
| server dvd
|
|
|
| server boot
|
|
|
| cloud boot
|
|
|
| cloud base disk
|
|
|
| cloud netinst
|
|
|
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.
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 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.
- ↑ Brief description about the warning status
|
{{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}}
|
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
Please click [show] in each table to view the tests of each media installation, and click [edit] to post your test results using the syntax in Key Section.
Image sanity
Default boot and install
Bare metal testing required
Running these tests in a virtualized environment is valuable, but the test must pass on bare metal using a physical install medium for each release-blocking image in each test environment at least for the final release candidate image (i.e. the released image) for each milestone.
Single test tableIn all of these tests, the test case used is
QA:Testcase_Boot_default_install. That is where the links point. The same test needs to be run for multiple images and target platforms. Note that the non-installer-based ARM disk images are covered by the later
#ARM disk images section.
| Milestone
|
Image
|
PKVM BE
|
PKVM LE
|
PVM
|
| Host |
Guest BE |
Guest LE
|
Host |
Guest BE |
Guest LE
|
LPAR BE |
LPAR LE
|
| Alpha
|
Server netinst
|
none
|
none
|
none
|
none
|
[1]
|
|
none
|
none
|
| Alpha
|
Server offline
|
none
|
|
none
|
none
|
|
|
none
|
none
|
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
PXE boot
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
USB media
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
Virtualization
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
Storage devices
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
Guided storage configuration
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
Guided storage shrinking
Environments
For this test, the column headings refer to the storage volume type to be shrunk, not the one chosen to replace it for the new installation.
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
Custom storage configuration
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
User interface
- ↑ strange colours
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
Installation repositories
Package sets
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
Kickstart
Upgrade
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
Internationalization and Localization
Miscellaneous
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
- ↑ Bug 122826 - qemu-le guest - TX virtqueue fails to be handled by vhost and falls back to QEMU
- ↑ boot local disk do not exist for ppc64/ppc64le grub2
