From Fedora Project Wiki

Revision as of 23:32, 4 November 2014 by Satellit (talk | contribs) (→‎Upgrade)

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.

This page records Installation validation testing test results for the Fedora 21 Final TC1 compose.

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

1. Download one or more media for testing: Template:Fedora 21 Final TC1 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-results command. 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.
Virtual machine testing
In most cases, testing in a virtual machine is OK. You can test UEFI (including SecureBoot) in VMs as well.

Results summary page

The Test Results:Fedora 21 Final TC1 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

  1. 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).
  2. Once reviewed, make your changes to any current documents that use the template (e.g. Test_Results:Current_Installation_Test).
  3. Lastly, update Template:Installation_test_matrix with the same changes.

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}}
Fail fail pboy [1] [2]
Failed - Same issue with LVM again
  1. RHBZ #2246871
  2. RHBZ #'2244305
{{result|fail|pboy|2246871|2244305}}
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

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

Milestone Test Case Server Workstation Spins ARM disks Cloud
Alpha / Final QA:Testcase_Mediakit_Checksums
none
none
none
none
none
Beta QA:Testcase_Mediakit_ISO_Size
none
none
none
none
Alpha QA:Testcase_Mediakit_Repoclosure
none
Alpha QA:Testcase_Mediakit_FileConflicts
none

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 table
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.
Milestone Image i386 x86_64 UEFI
Alpha Workstation live
none
Pass pass satellit
[1]
none
Alpha Server netinst
none
none
none
Alpha Server offline
none
none
none
Alpha KDE live
none
none
none
Optional Xfce live
none
none
none
Optional LXDE live
none
none
none
Optional MATE live
none
none
none
Optional SoaS live
none
Pass pass satellit
[2]
none
  1. DVD > HD
  2. DVD > HD

ARM disk images

Single test table
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.
Milestone Image Ext boot
Alpha Minimal
none
Alpha KDE
none
Optional Xfce
none
Optional Desktop
none
Optional LXDE
none
Optional MATE
none
Optional SoaS
none

Cloud images

Milestone Test case i386 x86_64
Alpha QA:Testcase_EC2_AMI_Validation
none
none
Alpha QA:Testcase_OpenStack_Image_Validation
none
none


PXE boot

Milestone Test Case i386 x86_64 ARM
Alpha QA:Testcase_Boot_Methods_Pxeboot
none
none
none

USB media

Milestone Test Case i386 x86_64 UEFI
Alpha QA:Testcase_USB_stick_Live LiveUSB-creator
none
none
none
Alpha QA:Testcase_USB_stick_Live Live-ISO-to-Disk
none
none
none
Alpha QA:Testcase_USB_stick_Live_dd
none
none
none
Alpha QA:Testcase_USB_stick_DVD Live-ISO-to-Disk
none
none
none
Alpha QA:Testcase_USB_stick_DVD_dd
none
none
none

Virtualization

Milestone Test Case x86 BIOS[1] x86 UEFI ARM
Beta QA:Testcase_Install_to_Previous_KVM
none
none
none
Beta QA:Testcase_Install_to_Current_KVM
none
none
none
Final QA:Testcase_Boot_Methods_Xen_Para_Virt
none
none
none
  1. 'x86' means 'x86_64 or i386'

Storage devices

Milestone Test Case x86[1] ARM
Alpha QA:Testcase_install_to_SATA
none
none
Alpha QA:Testcase_install_to_PATA
none
Alpha QA:Testcase_install_to_SCSI
none
none
Alpha QA:Testcase_install_to_SAS
none
Beta QA:Testcase_install_to_firmware_RAID
none
Beta QA:Testcase_install_to_hardware_RAID
none
Beta QA:Testcase_install_to_VirtIO
none
none
Final QA:Testcase_install_to_iSCSI_no_authentication
none
Final QA:Testcase_install_to_multipath
none
Final QA:Testcase_install_to_FCoE_target
none
  1. 'x86' means 'x86_64 or i386'

Guided storage configuration

Milestone Test Case x86 BIOS[1] x86 UEFI ARM
Alpha QA:Testcase_partitioning_guided_empty
none
none
none
Alpha QA:Testcase_partitioning_guided_delete_all
none
none
none
Alpha QA:Testcase_partitioning_guided_multi_select
none
none
Beta QA:Testcase_partitioning_guided_delete_partial
none
none
Beta QA:Testcase_partitioning_guided_free_space
none
none
Beta QA:Testcase_partitioning_guided_encrypted
none
none
none
Beta QA:Testcase_partitioning_guided_multi_empty_all
none
none
  1. 'x86' means 'x86_64 or i386'

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.
Milestone Test Case LVM ext4 NTFS BTRFS
Final QA:Testcase_partitioning_guided_shrink
none
none
none
none

Custom storage configuration

Milestone Test Case x86 BIOS[1] x86 UEFI ARM
Beta QA:Testcase_Partitioning_On_Software_RAID
none
none
Final QA:Testcase_anaconda_btrfs_rootfs_on_disk_partition
none
none
none
Final QA:Testcase_anaconda_ext3_rootfs_on_disk_partition
none
none
none
Final QA:Testcase_anaconda_xfs_rootfs_on_disk_partition
none
none
none
Optional QA:Testcase_Partitioning_No_Swap
none
none
none
  1. 'x86' means 'x86_64 or i386'

User interface

Milestone Test Case x86 ARM
Alpha QA:Testcase_Anaconda_User_Interface_Graphical
none
Alpha QA:Testcase_Anaconda_User_Interface_Basic_Video_Driver
none
Alpha QA:Testcase_Anaconda_User_Interface_Text
none
none
Alpha QA:Testcase_Anaconda_User_Interface_VNC
none
none
Alpha QA:Testcase_Anaconda_User_Interface_VNC_Vncconnect
none
none
Beta QA:Testcase_Anaconda_User_Interface_serial_console
none
none

Installation repositories

Milestone Test Case Result
Alpha QA:Testcase_install_repository_Mirrorlist_graphical
none
Alpha QA:Testcase_install_repository_HTTP/FTP_graphical
none
Alpha QA:Testcase_install_repository_HTTP/FTP_variation
none
Beta QA:Testcase_install_repository_NFS_graphical
none
Beta QA:Testcase_install_repository_NFS_variation
none
Final QA:Testcase_install_repository_NFSISO_variation
none
Final QA:Testcase_install_repository_Hard_drive_variation
none

Kickstart

Milestone Test Case Result
Alpha QA:Testcase_kickstart_user_creation
none
Beta QA:Testcase_Kickstart_Http_Server_Ks_Cfg
none
Beta QA:Testcase_Kickstart_File_Path_Ks_Cfg
none
Beta QA:Testcase_Kickstart_Hd_Device_Path_Ks_Cfg
none
Beta QA:Testcase_Kickstart_Nfs_Server_Path_Ks_Cfg
none

Upgrade

Milestone Test Case x86 BIOS[1] x86 UEFI ARM
Beta QA:Testcase_upgrade_fedup_cli_previous_desktop
Pass pass satellit
[2]
none
none
Beta QA:Testcase_upgrade_fedup_cli_previous_kde
Inprogress inprogress satellit
[3]
none
none
Beta QA:Testcase_upgrade_fedup_cli_previous_minimal
none
none
none
Beta QA:Testcase_upgrade_fedup_cli_previous_desktop_encrypted
none
none
none

Miscellaneous

Milestone Test Case x86 BIOS[1] x86 UEFI ARM
Alpha QA:Testcase_Anaconda_save_traceback_to_bugzilla
none
none
none
Alpha QA:Testcase_Anaconda_updates.img_via_URL
none
none
none
Alpha QA:Testcase_Anaconda_user_creation
none
none
none
Beta QA:Testcase_Anaconda_rescue_mode
none
none
Final QA:Testcase_dualboot_with_windows
none
none
Final QA:Testcase_dualboot_with_OSX
none
Final QA:Testcase_Anaconda_updates.img_via_installation_source
none
none
none
Final QA:Testcase_Anaconda_updates.img_via_local_media
none
none
none
Optional QA:Testcase_Install_Image_Boot_Local
none
Optional QA:Testcase_Memtest86
none
Optional QA:Testcase_Anaconda_traceback_debug_mode
none
none
none
  1. 'x86' means 'x86_64 or i386'