testing/wiki
10
0
Fork 3
generated from sig_core/wiki-template
Code Issues 1 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

migrate_to_testing_wiki #8

Merged
alangm merged 61 commits from tcooper/testing-wiki:migrate_to_testing_wiki into main 2024-04-26 01:34:01 +00:00
Conversation 0 Commits 61 Files Changed 66 +581 -41
15 changed files with 581 additions and 41 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit bd35f0cef5 - Show all commits

34
QA/Testcase_Bootloader_Disk_Selection.md Normal file
View File

@ -0,0 +1,34 @@
---
title: QA:Testcase Bootloader Disk Selection
author: Al Bowles
revision_date: 2022-07-08
rc:
prod: Rocky Linux
ver:
- 8
- 9
level: Final
---
!!! info "Associated release criterion"
This test case is associated with the [Release_Criteria#Bootloader Disk Selection](9_release_criteria.md#bootloader-disk-selection) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
## Description
This test case verifies that the user is able to select an alternative disk on which to install the bootloader. It also verifies that, if the user is so inclined, they may choose not to install a bootloader at all.
{% include 'testing/qa_data_loss_warning.md' %}
## Setup
{% include 'testing/qa_setup_boot_to_media.md' %}
## How to test
1. In the Installation Destination spoke, select the disk(s) to install to, then click the "Full disk summary and bootl loader..." button at the bottom of the screen: ![Full disk summary and bootloader...](/assets/images/bootloader.png){ loading=lazy }
1. Click the checkbox next to the disk on which the bootloader is desired
1. Alternatively, uncheck the boot checkbox next to all disks to skip bootloader installation
1. Proceed with installation on the test system.
## Expected Results
1. Installation should complete successfully.
1. Note that if no bootloader is installed, the system may not boot after installation is complete. This is expected.
{% include 'testing/qa_testcase_bottom.md' %}

61
QA/Testcase_Disk_Layouts.md Normal file
View File

@ -0,0 +1,61 @@
---
title: QA:Testcase Disk Layouts
author: Al Bowles
revision_date: 2022-07-08
rc:
prod: Rocky Linux
ver:
- 8
- 9
level: Final
---
!!! info "Associated release criterion"
This test case is associated with the [Release_Criteria#Disk Layouts](9_release_criteria.md#disk-layouts) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
## Description
This test case verifies successful installation to any supported partition layout using any file system or format combination.
{% include 'testing/qa_data_loss_warning.md' %}
## Setup
{% include 'testing/qa_setup_boot_to_media.md' %}
## How to test
1. Select the Installation Destination spoke.
1. Select the volumes to which the operating system should be installed.
1. Select the Custom radio button under the Storage Configuration section, then click "Done".
1. For each volume, perform these steps:
1. Choose the desired partitioning scheme from the dropdown menu. Supported options are Standard Partition, LVM, and LVM Thin Provisioning.
1. Select the "Encrypt my data" checkbox to create an encrypted filesystem.
1. Select the plus (+) button in the lower left hand corner to add a partition.
1. Define the desired mount point and volume capacity, then click "Add mount point".
1. Set the device type. Supported options are LVM, RAID, Standard Partition, and LVM Thin Provisioning.
1. If device type was set to RAID, select the RAID level. Supported options are RAID0, RAID1, RAID4, RAID5, RAID6, and RAID10.
1. Set the filesystem type. Supported options are BIOS Boot, ext2, ext3, ext4, swap, vfat, and xfs.
1. In supported cases you may choose to disable formatting of existing partitions by unchecking the Reformat checkbox.
1. When all partitions have been created, click the blue Done button in the upper left corner.
1. Review the Summary of Changes dialog, then click Accept Changes.
1. Continue the installation as normal.
## Expected Results
1. The installation should complete successfully and boot to the appropriate disk.
1. The specified filesystem type and partition scheme should be used.
1. If configured, software RAID should function as expected.
## Testing with openQA
The following openQA test suites satisfy this release criteria:
- `install_standard_partition_ext4`
- `install_custom_gui_standard_partition_ext4`
- `install_lvm_ext4`
- `install_custom_gui_lvm_ext4`
- `install_software_raid`
- `install_custom_gui_software_raid`
- `install_xfs`
- `install_custom_gui_xfs`
- `install_lvmthin`
- `install_multi`
- `install_multi_empty`
{% include 'testing/qa_testcase_bottom.md' %}

30
QA/Testcase_Firmware_RAID.md Normal file
View File

@ -0,0 +1,30 @@
---
title: QA:Testcase Firmware RAID
author: Al Bowles
revision_date: 2022-07-08
rc:
prod: Rocky Linux
ver:
- 8
- 9
level: Final
---
!!! info "Associated release criterion"
This test case is associated with the [Release_Criteria#Firmware RAID](9_release_criteria.md#firmware-raid) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
## Description
The installer must be able to detect and install to firmware RAID devices. Note that system-specific bugs do not count as blockers. It is likely that some hardware support might be broken or not available at all. DUDs (driver update disks) are not considered for this criteria.
## Setup
1. Add steps for setup for this Testcase.
## How to test
1. Do this first...
2. Then do this...
## Expected Results
1. This is what you should see/verify.
2. You should also see/verify this.
{% include 'testing/qa_testcase_bottom.md' %}

55
QA/Testcase_Installation_Interfaces.md Normal file
View File

@ -0,0 +1,55 @@
---
title: QA:Testcase Installation Interfaces
author: Al Bowles
revision_date: 2022-07-08
rc:
prod: Rocky Linux
ver:
- 8
- 9
level: Final
---
!!! info "Associated release criterion"
This test case is associated with the [Release_Criteria#Installation Interfaces](9_release_criteria.md#installation-interfaces) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
## Description
This test case verifies that the installer can complete an installation using all Anaconda spokes.
{% include 'testing/qa_data_loss_warning.md' %}
## Setup
{% include 'testing/qa_setup_boot_to_media.md' %}
## How to test
<!-- localization -->
1. Select a keyboard layout in the Keyboard Layout spoke
1. Set language support in the Language spoke
1. Set the system time and date in the Time and Date spoke
<!-- user settings -->
1. Set a root password in the Root Password spoke
1. Create a user in the user creation spoke
<!-- software -->
1. Select an installation source from the Installation Source spoke
1. Select a set of packages to install from the Package Selection spoke
<!-- system -->
1. Set a disk to which the operating system should install in the Installation Destination spoke
1. Set the kdump state from the Kdump spoke
1. Configure the system's network and hostname from the Network and Hostname spoke
1. Select a security policy from the Security Policy spoke
## Expected Results
1. The installation should complete and boot successfully.
## Testing in openQA
The following openQA test suites satisfy this release criteria:
- `install_arabic_language` OR `install_asian_language`
<!--
TODO
- something with kdump
- set hostname
- set security policy
-->
{% include 'testing/qa_testcase_bottom.md' %}

46
QA/Testcase_Installer_Help.md Normal file
View File

@ -0,0 +1,46 @@
---
title: QA:Testcase Installer Help
author: Al Bowles
revision_date: 2022-07-08
rc:
prod: Rocky Linux
ver:
- 8
- 9
level: Final
---
!!! info "Associated release criterion"
This test case is associated with the [Release_Criteria#Installer Help](9_release_criteria.md#installer-help) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
## Description
Any element in the installer which contains a “help” text must display the appropriate help documentation when selected.
## Setup
{% include 'testing/qa_setup_boot_to_media.md' %}
## How to test
1. From the Anaconda Hub, click the Help button in the upper right hand corner.
1. Verify that you see the "Customizing your Installation" help page.
1. Verify that the "Configuring language and location settings" link displays a topically appropriate page.
1. Close the Help browser to return to the Anaconda Hub.
1. Verify that the Localization help page displays for the Keyboard, Language Support, and Time & Date spokes:
1. Select the spoke, then click the Help button.
1. Verify that you see the "Configuring localization options" page containing a functioning link to the "Configuring keyboard, language, and time and date settings" page.
1. Close the Help browser (and click Done if necessary) to return to the Anaconda Hub.
1. Verify that the Help button in the Installation Source spoke displays the "Configuring installation source" page.
1. Verify that the Help button in the Software Selection spoke displays the "Configuring software selection" page.
1. Verify that the Help button in the Installation Destination spoke displays the "Configuring storage devices" page.
1. Verify that the Help button in the Network & Host Name spoke displays the "Configuring network and host name options" page.
1. Verify that the Help button in the Root Password spoke displays the "Configuring a root password" page.
1. Verify that the Help button in the User Creation spoke displays the "Creating a user account" page.
## Expected Results
1. All links should work and display relevant content.
## Testing in openQA
The following openQA test suites satisfy this release criteria:
- `anaconda_help`
{% include 'testing/qa_testcase_bottom.md' %}

37
QA/Testcase_Installer_Translations.md Normal file
View File

@ -0,0 +1,37 @@
---
title: QA:Testcase Installer Translations
author: Al Bowles
revision_date: 2022-07-08
rc:
prod: Rocky Linux
ver:
- 8
- 9
level: Final
---
!!! info "Associated release criterion"
This test case is associated with the [Release_Criteria#Installer Translations](9_release_criteria.md#installer-translations) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
## Description
The installer must correctly display all complete translations that are available for use.
## Setup
{% include 'testing/qa_setup_boot_to_media.md' %}
## How to test
1. From the Language Selection spoke, select a language.
## Expected Results
1. All spokes should display at least some of the content in the selected language.
2. It is expected to still see some content displayed in Latin characters even if a language that does not use Latin characters is selected.
## Testing in openQA
The following openQA test suites satisfy this release criteria:
- `install_asian_language`
- `install_arabic_language`
- `install_cyrillic_language`
- `install_european_language`
{% include 'testing/qa_testcase_bottom.md' %}

41
QA/Testcase_Kickstart_Installation.md Normal file
View File

@ -0,0 +1,41 @@
---
title: QA:Testcase Kickstart Installation
author: Al Bowles
revision_date: 2022-07-08
rc:
prod: Rocky Linux
ver:
- 8
- 9
level: Final
---
!!! info "Associated release criterion"
This test case is associated with the [Release_Criteria#Kickstart Installation](9_release_criteria.md#kickstart-installation) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
## Description
This test case verifies that installations via both local and remote Kickstart configuration files are successful.
{% include 'testing/qa_data_loss_warning.md' %}
## Setup
1. Copy a valid Kickstart file to a USB stick
1. Connect the USB stick to the test system
{% include 'testing/qa_setup_boot_to_media.md' %}
1. Hit the Tab key to edit the boot command
1. Provide a local Kickstart file by supplying the GRUB boot option `inst.ks=file:/path/to/local.ks` or a remote Kickstart file by supplying the GRUB boot option `inst.ks=https://dl.rockylinux.org/remote.ks`.
## How to test
1. Continue booting the installer as normal.
## Expected Results
1. The installation should complete and boot successfully, automatically populating the options specified in the Kickstart file.
## Testing in openQA
The following openQA test suites satisfy this release criteria:
- `install_kickstart_nfs`
- `server_realmd_join_kickstart`
<!-- TODO provide a test suite that does not require PARALLEL_WITH= -->
{% include 'testing/qa_testcase_bottom.md' %}

37
QA/Testcase_Minimal_Installation.md Normal file
View File

@ -0,0 +1,37 @@
---
title: QA:Testcase Minimal Installation
author: Al Bowles
revision_date: 2022-07-08
rc:
prod: Rocky Linux
ver:
- 8
- 9
level: Final
---
!!! info "Associated release criterion"
This test case is associated with the [Release_Criteria#Minimal Installation](9_release_criteria.md#minimal-installation) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
## Description
This test case verifies that a networked minimal installation is able to install the 'Minimal' package set. The installation should not require use of local packages to complete.
{% include 'testing/qa_data_loss_warning.md' %}
## Setup
{% include 'testing/qa_setup_boot_to_media.md' %}
## How to test
1. From the Installation Source spoke, configure a remote repository source from [MirrorManager](https://mirrors.rockylinux.org) appropriate to the architecture under test.
1. From the Software Selection spoke, select the Minimal package set.
1. Complete the installation using desired parameters.
## Expected Results
1. The installation should complete and boot successfully.
## Testing in openQA
The following openQA test suites satisfy this release criteria:
- `install_minimal`
{% include 'testing/qa_testcase_bottom.md' %}

37
QA/Testcase_Network_Attached_Storage.md Normal file
View File

@ -0,0 +1,37 @@
---
title: QA:Testcase Network Attached Storage
author: Al Bowles
revision_date: 2022-07-08
rc:
prod: Rocky Linux
ver:
- 8
- 9
level: Final
---
!!! info "Associated release criterion"
This test case is associated with the [Release_Criteria#Network Attached Storage](9_release_criteria.md#nas-network-attached-storage) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
## Description
The installer must be able to detect and install to supported NAS devices (if possible and supported by the kernel).
## Setup
1. Add steps for setup for this Testcase.
## How to test
### NFS
install nfs-utils
sudo mount -t nfs nfs-server:/nfs/path /mnt
then a created a file echo 1 > /mnt/1
verified it and permissions ls /mnt; cat /mnt/1
then deleted it rm /mnt/1
then unmounted sudo umount /mnt
### iSCSI
## Expected Results
1. This is what you should see/verify.
2. You should also see/verify this.
{% include 'testing/qa_testcase_bottom.md' %}

53
QA/Testcase_Packages_Installer_Sources.md Normal file
View File

@ -0,0 +1,53 @@
---
title: QA:Testcase Packages and Installer Sources
author: Al Bowles
revision_date: 2022-07-08
rc:
prod: Rocky Linux
ver: 8
level: Final
---
!!! info "Associated release criterion"
This test case is associated with the [Release_Criteria#Packages and Installer Sources](9_release_criteria.md#packages-installer-sources) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
## Description
This test case verifies that the installer can successfully install any of the supported package sets via any of the supported installer sources.
The following package sets are supported for installs from local media:
- server
- minimal
The following package sets are only available from remote sources and require a network connection:
- workstation
- graphical-server
- virtualization-host
{% include 'testing/qa_data_loss_warning.md' %}
## Setup
{% include 'testing/qa_setup_boot_to_media.md' %}
## How to test
1. For local package installations it is not necessary to enable networking or specify a mirror.
1. For package installation from remote sources:
1. From the Network and Hostname spoke, enable networking.
1. From the Installation Source spoke, configure a remote software source, supplying an appropriate [mirror](https://mirrors.rockylinux.org) for the version and architecture under test.
1. Complete the installer and wait for the machine to reboot.
## Expected Results
1. The installation should complete and boot successfully.
1. If a graphical package set was specified, the system should boot to a graphical login screen.
## Testing in openQA
The following openQA test suites satisfy this release criteria, provided they pass the `_do_install_reboot` module at a minimum:
- `install_packageset_server`
- `install_packageset_minimal`
- `install_packageset_workstation`
- `install_packageset_graphical-server`
- `install_packageset_virtualization-host`
{% include 'testing/qa_testcase_bottom.md' %}

54
QA/Testcase_Storage_Volume_Resize.md Normal file
View File

@ -0,0 +1,54 @@
---
title: QA:Testcase Storage Volume Resize
author: Al Bowles
revision_date: 2022-07-08
rc:
prod: Rocky Linux
ver:
- 8
- 9
level: Final
---
!!! info "Associated release criterion"
This test case is associated with the [Release_Criteria#Storage Volume Resize](9_release_criteria.md#storage-volume-resize) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
## Description
This test case verifies that the installer will successfully resize or delete and overwrite existing partitions on storage volumes.
{% include 'testing/qa_data_loss_warning.md' %}
## Setup
{% include 'testing/qa_setup_boot_to_media.md' %}
## How to test
### Resize
1. From the Installation Destination spoke, in the Storage Configuration section, select the Custom radio button, then click Done.
1. Expand the list of available partitions by clicking the black arrow to the left of the release version and architecture.
1. Select the partition you wish to resize. Be sure to uncheck the Reformat checkbox if you wish to resize without reformatting the partition.
1. Click the Update Settings button to save your settings.
1. Click the + button to create a new partition off of the existing partition. Provide a mount point and desired capacity, then click Add Mount Point.
1. Repeat as necessary for additional partitions, or click Done to return to the Anaconda main hub.
### Delete
1. From the Installation Destination spoke, in the Storage Configuration section, select the Automatic radio button, then click Done.
1. You should be presented with an "Installation Options" dialog, indicating the amount of disk space that is available for use and available to reclaim.
1. Click the Reclaim Space button.
1. Select a partition, then click the Delete button to delete the partition and reclaim the space.
1. Alternatively, click the Delete All button to delete all existing partitions.
1. When you have finished, click the Reclaim Space button to reclaim available free space.
## Expected Results
1. The installation should complete and boot successfully.
1. Resized partitions should correctly reflect the desired size. This may be verified using the `lsblk` command.
1. Deleted partitions should no longer exist.
## Testing in openQA
The following openQA test suites satisfy this release criteria:
- `install_delete_partial`
- `install_delete_pata`
- `install_resize_lvm`
{% include 'testing/qa_testcase_bottom.md' %}

51
QA/Testcase_Update_Image.md Normal file
View File

@ -0,0 +1,51 @@
---
title: QA:Testcase Update Image
author: Al Bowles
revision_date: 2022-07-08
rc:
prod: Rocky Linux
ver: 8
level: Final
---
!!! info "Associated release criterion"
This test case is associated with the [Release_Criteria#Update Image](9_release_criteria.md#update-image) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
## Description
<!-- TODO provide documentation on the topic of updates.img -->
This test case verifies that an [update image]() can be loaded into Anaconda and applied during the install process.
{% include 'testing/qa_data_loss_warning.md' %}
## Setup
{% include 'testing/qa_setup_boot_to_media.md' %}
1. Hit the Tab key to edit the boot command
## How to test
<!-- TODO host this internally -->
1. Supply `inst.updates=https://fedorapeople.org/groups/qa/updates/updates-openqa.img` to the GRUB command line
1. Boot into the installer as usual.
1. In Anaconda, open the Installation Destination spoke.
## Expected Results
1. Within the Installation Destination spoke, the selected install disk should have a pink background
=== "FAIL"
![No update provided - **FAIL**](/assets/images/no_updates.png){ loading=lazy }
=== "PASS"
![Update provided - **PASS**](/assets/images/updates.png){ loading=lazy }
1. If you cannot verify visually, check for the existence of `/tmp/updates`, which should contain updated source files if the update was successfully applied. Note that if the update image doesn't actually contain any source files, this directory will not be created.
<!-- TODO does /tmp/updates appear without completing installation? -->
## Testing with openQA
The following openQA test suites satisfy this release criteria:
- `install_scsi_updates_img`
## Additional References
[Red Hat Debug Boot Options](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/performing_an_advanced_rhel_installation/kickstart-and-advanced-boot-options_installing-rhel-as-an-experienced-user#debug-boot-options_kickstart-and-advanced-boot-options)<br>
[Fedora QA:Testcase Anaconda updates.img via URL](https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_URL)<br>
[Fedora QA:Testcase Anaconda updates.img via local media](https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_local_media)<br>
{% include 'testing/qa_testcase_bottom.md' %}

30
qa_test_cases.md
View File

@ -22,21 +22,21 @@ This page lists all test cases in work and who is working on them...
## Installer Requirements ## Installer Requirements
| Requirement | Test Case | Assignee | Status | | Requirement | Test Case | Assignee | Status |
| --------------------------------------------------- | ------------------------------------------------------------------------ | ----------------------- | --------------------------------------- | | --------------------------------------------------- | ----------------------------------------------------------------------------------------- | ----------------------- | --------------------------------------- |
| Media Consistency Verification | [QA:Testcase TBD](Testcase_Template.md) | @tbd | | | Media Consistency Verification | [QA:Testcase Media USB dd](Testcase_Media_USB_dd.md)<br>[QA:Testcase Boot Methods Boot ISO](Testcase_Boot_Methods_Boot_Iso.md)<br>[QA:Testcase Boot Methods DVD](Testcase_Boot_Methods_Dvd.md) | @raktajino | |
| Packages and Installer Sources | [QA:Testcase TBD](Testcase_Template.md) | @tbd | Implemented in openQA, document | | Packages and Installer Sources | [QA:Testcase Packages and Installer Sources](Testcase_Packages_Installer_Sources.md) | @raktajino | Implemented in openQA, document |
| NAS (Network Attached Storage) | [QA:Testcase TBD](Testcase_Template.md) | @tbd | | | NAS (Network Attached Storage) | [QA:Testcase Network Attached Storage](Testcase_Network_Attached_Storage.md) | @raktajino | |
| Installation Interfaces | [QA:Testcase TBD](Testcase_Template.md) | @tbd | Implemented in openQA, document | | Installation Interfaces | [QA:Testcase Installation Interfaces](Testcase_Installation_Interfaces.md) | @raktajino | Implemented in openQA, document |
| Minimal Installation | [QA:Testcase TBD](Testcase_Template.md) | @tbd | Implemented in openQA, document | | Minimal Installation | [QA:Testcase Minimal Installation](Testcase_Minimal_Installation.md) | @raktajino | Implemented in openQA, document |
| Kickstart Installation | [QA:Testcase TBD](Testcase_Template.md) | @tbd | Implemented in openQA, document | | Kickstart Installation | [QA:Testcase Kickstart Installation](Testcase_Kickstart_Installation.md) | @raktajino | Implemented in openQA, document |
| Disk Layouts | [QA:Testcase TBD](Testcase_Template.md) | @tbd | Implemented in openQA, document | | Disk Layouts | [QA:Testcase Disk Layouts](Testcase_Disk_Layouts.md) | @raktajino | Implemented in openQA, document |
| Firmware RAID | [QA:Testcase TBD](Testcase_Template.md) | @tbd | | | Firmware RAID | [QA:Testcase Firmware RAID](Testcase_Firmware_RAID.md) | @raktajino | |
| Bootloader Disk Selection | [QA:Testcase TBD](Testcase_Template.md) | @tbd | | | Bootloader Disk Selection | [QA:Testcase Bootloader Disk Selection](Testcase_Bootloader_Disk_Selection.md) | @raktajino | |
| Storage Volume Resize | [QA:Testcase TBD](Testcase_Template.md) | @tbd | Implemented in openQA, document | | Storage Volume Resize | [QA:Testcase Storage Volume Resize](Testcase_Storage_Volume_Resize.md) | @raktajino | Implemented in openQA, document |
| Update Image | [QA:Testcase TBD](Testcase_Template.md) | @tbd | Implemented in openQA, document | | Update Image | [QA:Testcase Update Image](Testcase_Update_Image.md) | @raktajino | Implemented in openQA, document |
| Installer Help | [QA:Testcase TBD](Testcase_Template.md) | @tbd | Implemented in openQA, document | | Installer Help | [QA:Testcase Installer Help](Testcase_Installer_Help.md) | @raktajino | Implemented in openQA, document |
| Installer Translations | [QA:Testcase TBD](Testcase_Template.md) | @tbd | Implemented in openQA, document | | Installer Translations | [QA:Testcase Installer Translations](Testcase_Installer_Translations.md) | @raktajino | Implemented in openQA, document |
## Cloud Image Requirements ## Cloud Image Requirements

28
release_criteria/r8/8_release_criteria.md
View File

@ -84,79 +84,81 @@ Assets and functionality that are Red Hat specific should not be included. If th
This means that the installer’s mechanism for verifying the install medium is intact and must complete successfully, with the assumption that the medium was correctly written. It should return a failure message if this not the case. This means that the installer’s mechanism for verifying the install medium is intact and must complete successfully, with the assumption that the medium was correctly written. It should return a failure message if this not the case.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Media USB dd](Testcase_Media_USB_dd.md)
- [QA:Testcase Boot Methods Boot ISO](Testcase_Boot_Methods_Boot_Iso.md)
- [QA:Testcase Boot Methods DVD](Testcase_Boot_Methods_Dvd.md)
#### Packages and Installer Sources #### Packages and Installer Sources
The installer must be able to use all supported local/remote packages and installer sources. The installer must be able to use all supported local/remote packages and installer sources.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Packages and Installer Sources](Testcase_Packages_Installer_Sources.md)
#### NAS (Network Attached Storage)" #### NAS (Network Attached Storage)"
The installer must be able to detect and install to supported NAS devices (if possible and supported by the kernel). The installer must be able to detect and install to supported NAS devices (if possible and supported by the kernel).
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Network Attached Storage](Testcase_Network_Attached_Storage.md)
#### Installation Interfaces #### Installation Interfaces
The installer must be able to complete an installation using all supported spokes. The installer must be able to complete an installation using all supported spokes.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Installation Interfaces](Testcase_Installation_Interfaces.md)
#### Minimal Installation #### Minimal Installation
A minimal installation (via network) must be able to install the minimal package set. A minimal installation (via network) must be able to install the minimal package set.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Minimal Installation](Testcase_Minimal_Installation.md)
#### Kickstart Installation #### Kickstart Installation
A kickstart installation should succeed, whether from optical/USB media or via the network. A kickstart installation should succeed, whether from optical/USB media or via the network.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Kickstart Installation](Testcase_Kickstart_Installation.md)
#### Disk Layouts #### Disk Layouts
The installer must be able to create and install to any workable partition layout using any file system or format combination offered or supported by the installer. File systems that are not supported by the EL kernel is not tested here (this means btrfs, zfs, both of wish are not supported). The installer must be able to create and install to any workable partition layout using any file system or format combination offered or supported by the installer. File systems that are not supported by the EL kernel is not tested here (this means btrfs, zfs, both of wish are not supported).
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Disk Layouts](Testcase_Disk_Layouts.md)
#### Firmware RAID #### Firmware RAID
The installer must be able to detect and install to firmware RAID devices. Note that system-specific bugs do not count as blockers. It is likely that some hardware support might be broken or not available at all. DUDs (driver update disks) are not considered for this criteria. The installer must be able to detect and install to firmware RAID devices. Note that system-specific bugs do not count as blockers. It is likely that some hardware support might be broken or not available at all. DUDs (driver update disks) are not considered for this criteria.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Firmware RAID](Testcase_Firmware_RAID.md)
#### Bootloader Disk Selection #### Bootloader Disk Selection
The installer must allow the user to choose which disk the bootloader will be installed to or, if the user so chooses, not to install a bootloader. The installer must allow the user to choose which disk the bootloader will be installed to or, if the user so chooses, not to install a bootloader.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Bootloader Disk Selection](Testcase_Bootloader_Disk_Selection.md)
#### Storage Volume Resize #### Storage Volume Resize
Any installer mechanism for resizing storage volumes must correctly attempt the requested operation. This means that if the installer offers a way to resize storage volumes, then it must use the correct resizing tool with the correct parameters. However, it does not require the installer to disallow resizing of unformatted or volumes with an unknown filesystem type. Any installer mechanism for resizing storage volumes must correctly attempt the requested operation. This means that if the installer offers a way to resize storage volumes, then it must use the correct resizing tool with the correct parameters. However, it does not require the installer to disallow resizing of unformatted or volumes with an unknown filesystem type.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Storage Volume Resize](Testcase_Storage_Volume_Resize.md)
#### Update Image #### Update Image
The installer must be able to use an installer update image retrieved from removable media or a remote package source. This includes DUDs (driver update disks). The installer must be able to use an installer update image retrieved from removable media or a remote package source. This includes DUDs (driver update disks).
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Update Image](Testcase_Update_Image.md)
#### Installer Help #### Installer Help
Any element in the installer which contains a “help” text must display the appropriate help documentation when selected. Any element in the installer which contains a “help” text must display the appropriate help documentation when selected.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Installer Help](Testcase_Installer_Help.md)
#### Installer Translations #### Installer Translations
The installer must correctly display all complete translations that are available for use. The installer must correctly display all complete translations that are available for use.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Installer Translations](Testcase_Installer_Translations.md)
### Cloud Image Requirements ### Cloud Image Requirements
#### Images Published to Cloud Providers #### Images Published to Cloud Providers

28
release_criteria/r9/9_release_criteria.md
View File

@ -84,79 +84,81 @@ Assets and functionality that are Red Hat specific should not be included. If th
This means that the installer’s mechanism for verifying the install medium is intact and must complete successfully, with the assumption that the medium was correctly written. It should return a failure message if this not the case. This means that the installer’s mechanism for verifying the install medium is intact and must complete successfully, with the assumption that the medium was correctly written. It should return a failure message if this not the case.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Media USB dd](Testcase_Media_USB_dd.md)
- [QA:Testcase Boot Methods Boot ISO](Testcase_Boot_Methods_Boot_Iso.md)
- [QA:Testcase Boot Methods DVD](Testcase_Boot_Methods_Dvd.md)
#### Packages and Installer Sources #### Packages and Installer Sources
The installer must be able to use all supported local/remote packages and installer sources. The installer must be able to use all supported local/remote packages and installer sources.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Packages and Installer Sources](Testcase_Packages_Installer_Sources.md)
#### NAS (Network Attached Storage)" #### NAS (Network Attached Storage)"
The installer must be able to detect and install to supported NAS devices (if possible and supported by the kernel). The installer must be able to detect and install to supported NAS devices (if possible and supported by the kernel).
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Network Attached Storage](Testcase_Network_Attached_Storage.md)
#### Installation Interfaces #### Installation Interfaces
The installer must be able to complete an installation using all supported spokes. The installer must be able to complete an installation using all supported spokes.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Installation Interfaces](Testcase_Installation_Interfaces.md)
#### Minimal Installation #### Minimal Installation
A minimal installation (via network) must be able to install the minimal package set. A minimal installation (via network) must be able to install the minimal package set.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Minimal Installation](Testcase_Minimal_Installation.md)
#### Kickstart Installation #### Kickstart Installation
A kickstart installation should succeed, whether from optical/USB media or via the network. A kickstart installation should succeed, whether from optical/USB media or via the network.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Kickstart Installation](Testcase_Kickstart_Installation.md)
#### Disk Layouts #### Disk Layouts
The installer must be able to create and install to any workable partition layout using any file system or format combination offered or supported by the installer. File systems that are not supported by the EL kernel is not tested here (this means btrfs, zfs, both of wish are not supported). The installer must be able to create and install to any workable partition layout using any file system or format combination offered or supported by the installer. File systems that are not supported by the EL kernel is not tested here (this means btrfs, zfs, both of wish are not supported).
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Disk Layouts](Testcase_Disk_Layouts.md)
#### Firmware RAID #### Firmware RAID
The installer must be able to detect and install to firmware RAID devices. Note that system-specific bugs do not count as blockers. It is likely that some hardware support might be broken or not available at all. DUDs (driver update disks) are not considered for this criteria. The installer must be able to detect and install to firmware RAID devices. Note that system-specific bugs do not count as blockers. It is likely that some hardware support might be broken or not available at all. DUDs (driver update disks) are not considered for this criteria.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Firmware RAID](Testcase_Firmware_RAID.md)
#### Bootloader Disk Selection #### Bootloader Disk Selection
The installer must allow the user to choose which disk the bootloader will be installed to or, if the user so chooses, not to install a bootloader. The installer must allow the user to choose which disk the bootloader will be installed to or, if the user so chooses, not to install a bootloader.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Bootloader Disk Selection](Testcase_Bootloader_Disk_Selection.md)
#### Storage Volume Resize #### Storage Volume Resize
Any installer mechanism for resizing storage volumes must correctly attempt the requested operation. This means that if the installer offers a way to resize storage volumes, then it must use the correct resizing tool with the correct parameters. However, it does not require the installer to disallow resizing of unformatted or volumes with an unknown filesystem type. Any installer mechanism for resizing storage volumes must correctly attempt the requested operation. This means that if the installer offers a way to resize storage volumes, then it must use the correct resizing tool with the correct parameters. However, it does not require the installer to disallow resizing of unformatted or volumes with an unknown filesystem type.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Storage Volume Resize](Testcase_Storage_Volume_Resize.md)
#### Update Image #### Update Image
The installer must be able to use an installer update image retrieved from removable media or a remote package source. This includes DUDs (driver update disks). The installer must be able to use an installer update image retrieved from removable media or a remote package source. This includes DUDs (driver update disks).
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Update Image](Testcase_Update_Image.md)
#### Installer Help #### Installer Help
Any element in the installer which contains a “help” text must display the appropriate help documentation when selected. Any element in the installer which contains a “help” text must display the appropriate help documentation when selected.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Installer Help](Testcase_Installer_Help.md)
#### Installer Translations #### Installer Translations
The installer must correctly display all complete translations that are available for use. The installer must correctly display all complete translations that are available for use.
??? tldr "References" ??? tldr "References"
- Test cases: - Test cases:
- [QA:Testcase TBD](Testcase_Template.md) - [QA:Testcase Installer Translations](Testcase_Installer_Translations.md)
### Cloud Image Requirements ### Cloud Image Requirements
#### Images Published to Cloud Providers #### Images Published to Cloud Providers