|Line 831:||Line 831:|
Revision as of 07:14, 18 September 2014
This page is intended to record installation validation testing test results for the Fedora 21 Alpha RC1 milestone.
- 1 Instructions
- 2 Test Matrix
This page tracks test results against the Fedora 21 Alpha RC1 build. Test results against other Fedora 21 milestones can be found at Category:Fedora_21_Test_Results. The explanation of test case priority is available in the release validation test plan.
What To Test
- Download the required ISO images for the candidate build under test. 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 install 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.
The following cast of characters will be available testing, workarounds, bug fixes, general discussion ...
Add or Remove a Test Case
- Please request review for your changes by publishing your test case for review to test list.
- Once reviewed, make your changes to this document
- Finally, update QA:Fedora_21_Install_Results_Template with the same changes.
See the table below for a sample format for test results. All test results are posted using the format specified Template:Result.
|Test Results Format|
|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.
|Image sanity tests|
Default boot and install
In 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.
|Default boot and install|
- Workstation Live
- RHBZ #1142862
- just a VM
- f21-tC6 - last build with kickstart.file before naming change error
|USB stick tests|
- Wks x86_64
- KDE i386 (disks)
ARM disk images
In all of these tests, the test case used is QA:Testcase_arm_image_deployment. That is where the links point. The same test needs to be run for multiple images and target platforms.
|ARM disk image functionality|
- no image
|PXE boot tests|
Storage device tests
|Storage device tests|
- 'x86' means 'x86_64 or i386'
- virt test
Storage volume type tests
|Storage volume type tests|
- 'x86' means 'x86_64 or i386'
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.
|Release Level||Test Case||LVM||ext4||NTFS||BTRFS|