- 1 Which tests to run
- 2 How to test
- 3 Key
- 4 Test Matrix
- 4.1 Image sanity
- 4.2 Default boot and install
- 4.3 Fedora Media Writer
- 4.4 PXE boot
- 4.5 Virtualization
- 4.6 Storage devices
- 4.7 Guided storage configuration
- 4.8 Guided storage shrinking
- 4.9 Custom storage configuration
- 4.10 User interface
- 4.11 Installation repositories
- 4.12 Package sets
- 4.13 Kickstart
- 4.14 Upgrade
- 4.15 Internationalization and Localization
- 4.16 Miscellaneous
Which tests to 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:
|nightly compose path||Rawhide nightly path f27 nighly path||Rawhide nightly path f27 nighly path|
|server dvd||Beta-1.3 Beta-1.5 RC-1.6||Beta-1.3 Beta-1.5 RC-1.6|
|server netinst||Beta-1.3 Beta-1.5 RC-1.6||Beta-1.3 Beta-1.5 RC-1.6|
|cloud netinst||None||Beta-1.3 Beta-1.5 RC-1.6|
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.
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.
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.|
|Passed - The test has been run and the tester determine the test met the expected results|
|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.|
|Failed - Indicates a failed test. A link to a bug must be provided. See Template:Result for details on providing bug information.|
|||Warning - This test completed and met the expected results of the test, but other issues were encountered during testing that warrant attention.
|Multiple results - More people can easily provide results to a single test case.|
|Result from previous test run - This test result is directly moved from the test run of previous <build>.|
|Unsupported - An unsupported test or configuration. No testing is required.|
Please click [show] in each table to view the tests of each media installation, and click  to post your test results using the syntax in Key Section.
|Alpha / Final||QA:Testcase_Mediakit_Checksums|
|Milestone||Test Case||Bare Metal||PKVM BE||PKVM LE||PVM|
|BE||LE||Guest BE||Guest LE||Guest BE||Guest LE||LPAR BE||LPAR LE|
- RHBZ #1497720