generated from sig_core/wiki-template
Merge pull request 'migrate_to_testing_wiki' (#8) from tcooper/testing-wiki:migrate_to_testing_wiki into main
All checks were successful
mkdocs build / build (push) Successful in 33s
All checks were successful
mkdocs build / build (push) Successful in 33s
Reviewed-on: #8 Checked the browser pages in development box and the migration has worked correctly. There are a number of updates required to the migrated files but I view that as a separate issue to be addressed later. This PR is ready for merge.
This commit is contained in:
commit
b1cbdac530
@ -1,4 +1,6 @@
|
||||
---
|
||||
nav:
|
||||
- ... | index.md
|
||||
- QA:Test Cases: qa_test_cases.md
|
||||
- Wiki Development Guides: dev_guides
|
||||
...
|
||||
|
||||
2
docs/documentation/QA/.pages
Normal file
2
docs/documentation/QA/.pages
Normal file
@ -0,0 +1,2 @@
|
||||
---
|
||||
hide: true
|
||||
44
docs/documentation/QA/Testcase_Basic_Graphics_Mode.md
Normal file
44
docs/documentation/QA/Testcase_Basic_Graphics_Mode.md
Normal file
@ -0,0 +1,44 @@
|
||||
---
|
||||
title: QA:Testcase Basic Graphics Mode
|
||||
author: Trevor Cooper
|
||||
revision_date: 2022-06-23
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver: 8
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! error "REFERENCED RELEASE CRITERIA IS OVERLY GENERAL AND UNTESTABLE"
|
||||
The associated release criteria, [Release_Criteria#basic-graphics-mode-behaviors](8_release_criteria.md#basic-graphics-mode-behaviors), for this test case is overly general and **must** be modified to specific enough to be testable.
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#basic-graphics-mode-behaviors](8_release_criteria.md#basic-graphics-mode-behaviors) 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 will verify that release-blocking installers function as intended using the generic video driver option (“basic graphics mode”) on supported systems and classes of hardware.
|
||||
|
||||
{% include 'qa_testcase_supported_systems.md' %}
|
||||
|
||||
## Setup
|
||||
1. Obtain access to supported system and hardware class to be installed.
|
||||
2. Prepare appropriate media for the selected ISO to be tested.
|
||||
- Example: [QA:Testcase Media USB dd](Testcase_Media_USB_dd.md)
|
||||
|
||||
## How to test
|
||||
1. Boot the system from the prepared optical, USB media or virtual device attachment.
|
||||
- Examples: [QA:Testcase Boot Methods Boot ISO](Testcase_Boot_Methods_Boot_Iso.md), [QA:Testcase Boot Methods DVD](Testcase_Boot_Methods_Dvd.md)
|
||||
2. In the boot menu select the appropriate option to boot the installer.
|
||||
3. In the installer select the appropriate option to intall in basic graphics mode.
|
||||
4. Proceed with installation on the test system.<br>**Depending on installer choices this MAY destroy all the data on the test system.**
|
||||
|
||||
!!! error "DATA LOSS"
|
||||
If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.
|
||||
|
||||
## Expected Results
|
||||
1. Selection of basic graphics mode in the Anaconda installer is possible.
|
||||
2. Anaconda installer presents a usable graphical intallation environment.
|
||||
3. System under test can be installed normally.
|
||||
4. After reboot system boots into graphical environment.
|
||||
5. After login user is able to operate the graphical environment.
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
28
docs/documentation/QA/Testcase_Boot_Methods_Boot_Iso.md
Normal file
28
docs/documentation/QA/Testcase_Boot_Methods_Boot_Iso.md
Normal file
@ -0,0 +1,28 @@
|
||||
---
|
||||
title: QA:Testcase Boot Methods Boot Iso
|
||||
author: Trevor Cooper
|
||||
revision_date: 2022-05-18
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver: 8
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#initialization-requirements](9_release_criteria.md#initialization-requirements) 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 is to verify that the Anaconda installer starts correctly when booting from the Rocky Linux boot.iso.
|
||||
|
||||
## Setup
|
||||
1. Prepare your system for booting the boot.iso image. This may involve writing the image to a USB key or burning it to an optical disk. Additionally, attaching the boot.iso to a virtual machine instance as a Virtual Optical Disk or mounting the boot.iso to server via baseboard management controller virtual media attach should be possible but is not expressly required.
|
||||
|
||||
## How to test
|
||||
1. Boot the system from the prepared optical, USB media or virtual device attachment.
|
||||
2. In the boot menu select the appropriate option to boot the installer.
|
||||
|
||||
## Expected Results
|
||||
1. Graphical boot menu is displayed for users to select install options. Navigating the menu and selecting entries must work. If no option is selected, the installer should load after a reasonable timeout.
|
||||
2. System boots into the Anaconda installer.
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
28
docs/documentation/QA/Testcase_Boot_Methods_Dvd.md
Normal file
28
docs/documentation/QA/Testcase_Boot_Methods_Dvd.md
Normal file
@ -0,0 +1,28 @@
|
||||
---
|
||||
title: QA:Testcase Boot Methods DVD
|
||||
author: Trevor Cooper
|
||||
revision_date: 2022-05-18
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver: 8
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#initialization-requirements](9_release_criteria.md#initialization-requirements) 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 is to verify that the Anaconda installer starts correctly when booting from DVD.iso.
|
||||
|
||||
## Setup
|
||||
1. Prepare your system for booting the DVD.iso image. This may involve writing the image to a USB key or burning it to an optical disk of sufficient capacity. Additionally, attaching the DVD.iso to a virtual machine instance as a Virtual Optical Disk or mounting the DVD.iso to server via baseboard management controller virtual media attach should be possible but is not expressly required.
|
||||
|
||||
## How to test
|
||||
1. Boot the system from the prepared optical, USB media or virtual device attachment.
|
||||
2. In the boot menu select the appropriate option to boot the installer.
|
||||
|
||||
## Expected Results
|
||||
1. Graphical boot menu is displayed for users to select install options. Navigating the menu and selecting entries must work. If no option is selected, the installer should load after a reasonable timeout.
|
||||
2. System boots into the Anaconda installer.
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
34
docs/documentation/QA/Testcase_Bootloader_Disk_Selection.md
Normal file
34
docs/documentation/QA/Testcase_Bootloader_Disk_Selection.md
Normal 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 'qa_data_loss_warning.md' %}
|
||||
|
||||
## Setup
|
||||
{% include '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: { 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 'qa_testcase_bottom.md' %}
|
||||
@ -0,0 +1,32 @@
|
||||
---
|
||||
title: QA:Testcase Custom Boot Methods Boot Iso
|
||||
author: Trevor Cooper
|
||||
revision_date: 2022-06-23
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver: 9
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#vnc-graphics-mode-behaviors](9_release_criteria.md#vnc-graphics-mode-behaviors) 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 is to verify that the Anaconda installer starts correctly when booting from the Rocky Linux boot.iso using a custom kernel command line.
|
||||
|
||||
## Setup
|
||||
1. Prepare your system for booting the boot.iso image. This may involve writing the image to a USB key or burning it to an optical disk. Additionally, attaching the boot.iso to a virtual machine instance as a Virtual Optical Disk or mounting the boot.iso to server via baseboard management controller virtual media attach should be possible but is not expressly required.
|
||||
|
||||
## How to test
|
||||
1. Boot the system from the prepared optical, USB media or virtual device attachment.
|
||||
2. In the boot menu select the appropriate option to boot the installer.
|
||||
3. Interrupt the normal boot and edit the kernel command line.
|
||||
4. Add appropriate/required options to the kernel command line and resume booting into the installer.
|
||||
- Example: For network install from an alternate repository add `--inst.url=http://<server>/<path_to_BaseOS_repo>` and (optionally) `--inst.repo=AppStream,http://<server>/<path_to_AppStream_repo>` to the kernel command line.
|
||||
- Example: For VNC install in **Direct Mode** add `--inst.vnc` to the kernel command line. For VNC install in **Connect Mode** add `--inst.vnc` and `--inst.vncserver=<host>:<port>` to the kernel command line.
|
||||
|
||||
## Expected Results
|
||||
1. Boot menu is displayed for users to select install options. Navigating the menu and selecting entries must work. Editing the boot command line must be possible. If no option is selected, the installer should load after a reasonable timeout.
|
||||
2. System boots into the Anaconda installer and any command line options specified are utilized.
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
200
docs/documentation/QA/Testcase_Debranding.md
Normal file
200
docs/documentation/QA/Testcase_Debranding.md
Normal file
@ -0,0 +1,200 @@
|
||||
---
|
||||
title: QA:Testcase Debranding
|
||||
author: Trevor Cooper
|
||||
revision_date: 2022-05-18
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver: 8
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria - Debranding](9_release_criteria.md#debranding) 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 Rocky Linux [Release Engineering Team](/team/release_engineering/) builds and maintains tools to manage the debranding of packages received from the upstream vendor. They have published a comprehensive [debranding guide](/team/release_engineering/debranding/) and maintain a [list of packages](https://git.rockylinux.org/rocky/metadata/-/blob/main/patch.yml) requiring debranding patches.
|
||||
|
||||
This testcase will verify that all packages available on released media that Rocky Linux Release Engineering has identified as requiring debranding are debranded successfully per their specification.
|
||||
|
||||
## Setup
|
||||
1. Obtain access to an environment with the `dnf`, and `koji` commands and access to [Rocky Linux Gitlab](https://git.rockylinux.org) and [Rocky Linux Koji](https://koji.rockylinux.org)
|
||||
2. Download the ISO to be tested to test machine.
|
||||
3. Configure `/etc/koji.conf` to access the [Rocky Linux Koji](https://koji.rockylinux.org).
|
||||
4. Download a recent copy the [patch.yml](https://git.rockylinux.org/rocky/metadata/-/blob/main/patch.yml) from [Rocky Linux Gitlab](https://git.rockylinux.org).
|
||||
|
||||
!!! info "patch.yml"
|
||||
Packages listed in `patch.yml` are names of source RPMs. Binary RPMs containing content produced by building the patched source RPMs need to be validated. The easiest way to get the list of all possible binary RPMs for a particular package and arch is to ask obtain that information in koji.
|
||||
|
||||
## How to test
|
||||
1. Mount the ISO to be tested locally.
|
||||
- Example:
|
||||
```
|
||||
$ mount -o loop Rocky-8.5-x86_64-dvd1.iso /media
|
||||
```
|
||||
2. Determine the path(s) to the `repodata` directory(ies) on the ISO.
|
||||
- Example:
|
||||
```
|
||||
$ find /media -name repodata
|
||||
```
|
||||
3. For each package to be validated get the names of the `noarch` and `<arch>` specific packages created from it.
|
||||
- Example:
|
||||
```
|
||||
$ koji --quiet latest-build --arch=x86_64 dist-rocky8-compose <package>
|
||||
$ koji --quiet latest-build --arch=noarch dist-rocky8-compose <package>
|
||||
```
|
||||
4. Use `dnf` to obtain the paths to the binary packages requiring debranding.
|
||||
- Example:
|
||||
```
|
||||
$ dnf download --urls --repofrompath BaseOS,/media/BaseOS --repo BaseOS \
|
||||
--repofrompath Minimal,/media/Minimal --repo Minimal \
|
||||
<binary_package>
|
||||
```
|
||||
5. Copy the `<binary_package>` from the media and examine it's metadata and/or contents to determine if it has obviously been patched.
|
||||
- Example:
|
||||
```
|
||||
$ rpm -q --changelog -p <path_to_binary_package> | head | \
|
||||
grep "Release Engineering <releng@rockylinux.org>" -C2 | \
|
||||
grep -Eq "<pattern_to_find>"
|
||||
|
||||
$ rpm2cpio <path_to_binary_package> |
|
||||
cpio --quiet --extract --to-stdout .<file_to_examine> | \
|
||||
grep -Eq "<pattern_to_find>"
|
||||
```
|
||||
|
||||
!!! info "NOTE"
|
||||
Note all debranding patches will patch files directly and leave very obvious traces, some patches don't even add changelog messages to use as an indicator that the package has been patched or debranded. Sometimes the only solution is to extract the binary package and examine the contents directly to find something to test.
|
||||
|
||||
6. Unmount the ISO.
|
||||
- Example:
|
||||
```
|
||||
$ umount /media
|
||||
```
|
||||
|
||||
## Expected Results
|
||||
1. Packages tracked by Release Engineering as requiring debranding and published on installation media are, in fact, debranded per their specification.
|
||||
|
||||
<h3>Sample Output</h3>
|
||||
|
||||
=== "Success"
|
||||
|
||||
```
|
||||
$ sudo mount -o loop Rocky-8.5-aarch64-minimal.iso /media
|
||||
mount: /media: WARNING: device write-protected, mounted read-only.
|
||||
|
||||
$ find /media -name repodata
|
||||
/media/BaseOS/repodata
|
||||
/media/Minimal/repodata
|
||||
|
||||
$ curl -LOR https://git.rockylinux.org/rocky/metadata/-/raw/main/patch.yml
|
||||
% Total % Received % Xferd Average Speed Time Time Time Current
|
||||
Dload Upload Total Spent Left Speed
|
||||
100 3410 100 3410 0 0 20419 0 --:--:-- --:--:-- --:--:-- 20419
|
||||
|
||||
$ yq .debrand.all[] patch.yml | column -x -c 100 -o " "
|
||||
abrt anaconda anaconda-user-help chrony
|
||||
cloud-init cockpit crash dhcp
|
||||
dnf firefox fwupd gcc
|
||||
gcc-toolset-9-gcc gcc-toolset-10-gcc gcc-toolset-11-gcc gcc-toolset-12-gcc
|
||||
gnome-settings-daemon grub2 httpd initial-setup
|
||||
kernel kernel-rt libdnf libreoffice
|
||||
libreport nginx opa-ff opa-fm
|
||||
openscap pesign PackageKit python-pip
|
||||
python3 redhat-rpm-config scap-security-guide shim
|
||||
shim-unsigned-x64 shim-unsigned-aarch64 sos subscription-manager
|
||||
systemd thunderbird WALinuxAgent
|
||||
|
||||
$ ./yq .debrand.r8[] patch.yml | column -x -c 100 -o " "
|
||||
dotnet3.0 fwupdate gnome-boxes libguestfs pcs plymouth
|
||||
python2
|
||||
|
||||
NOTE: Only a single package will be shown in this Example.
|
||||
|
||||
$ koji --quiet latest-build --arch=x86_64 dist-rocky8-compose sos
|
||||
|
||||
$ koji --quiet latest-build --arch=noarch dist-rocky8-compose sos
|
||||
sos-4.1-9.el8_5.rocky.3.noarch
|
||||
sos-audit-4.1-9.el8_5.rocky.3.noarch
|
||||
|
||||
$ dnf download --urls --repofrompath BaseOS,/media/BaseOS --repo BaseOS \
|
||||
--repofrompath Minimal,/media/Minimal --repo Minimal \
|
||||
sos sos-audit | grep -E "^file"
|
||||
file:///media/BaseOS/Packages/s/sos-4.1-5.el8.noarch.rpm
|
||||
file:///media/BaseOS/Packages/s/sos-audit-4.1-5.el8.noarch.rpm
|
||||
|
||||
$ rpm -q --changelog -p /media/BaseOS/Packages/s/sos-4.1-5.el8.noarch.rpm | \
|
||||
head | grep "Release Engineering <releng@rockylinux.org>" -C2
|
||||
* Mon Oct 18 2021 Release Engineering <releng@rockylinux.org> - 4.1-5
|
||||
- Remove Red Hat branding from sos
|
||||
$ echo $?
|
||||
0
|
||||
|
||||
$ rpm -q --changelog -p /media/BaseOS/Packages/s/sos-audit-4.1-5.el8.noarch.rpm | \
|
||||
head | grep "Release Engineering <releng@rockylinux.org>" -C2
|
||||
* Mon Oct 18 2021 Release Engineering <releng@rockylinux.org> - 4.1-5
|
||||
- Remove Red Hat branding from sos
|
||||
$ echo $?
|
||||
0
|
||||
|
||||
$ umount /media
|
||||
```
|
||||
|
||||
=== "Failure"
|
||||
|
||||
```
|
||||
$ sudo mount -o loop Rocky-8.5-aarch64-minimal.iso /media
|
||||
mount: /media: WARNING: device write-protected, mounted read-only.
|
||||
|
||||
$ find /media -name repodata
|
||||
/media/BaseOS/repodata
|
||||
/media/Minimal/repodata
|
||||
|
||||
$ curl -LOR https://git.rockylinux.org/rocky/metadata/-/raw/main/patch.yml
|
||||
% Total % Received % Xferd Average Speed Time Time Time Current
|
||||
Dload Upload Total Spent Left Speed
|
||||
100 3410 100 3410 0 0 20419 0 --:--:-- --:--:-- --:--:-- 20419
|
||||
|
||||
$ yq .debrand.all[] patch.yml | column -x -c 100 -o " "
|
||||
abrt anaconda anaconda-user-help chrony
|
||||
cloud-init cockpit crash dhcp
|
||||
dnf firefox fwupd gcc
|
||||
gcc-toolset-9-gcc gcc-toolset-10-gcc gcc-toolset-11-gcc gcc-toolset-12-gcc
|
||||
gnome-settings-daemon grub2 httpd initial-setup
|
||||
kernel kernel-rt libdnf libreoffice
|
||||
libreport nginx opa-ff opa-fm
|
||||
openscap pesign PackageKit python-pip
|
||||
python3 redhat-rpm-config scap-security-guide shim
|
||||
shim-unsigned-x64 shim-unsigned-aarch64 sos subscription-manager
|
||||
systemd thunderbird WALinuxAgent
|
||||
|
||||
$ ./yq .debrand.r8[] patch.yml | column -x -c 100 -o " "
|
||||
dotnet3.0 fwupdate gnome-boxes libguestfs pcs plymouth
|
||||
python2
|
||||
|
||||
NOTE: Only a single package will be shown in this Example.
|
||||
|
||||
$ koji --quiet latest-build --arch=x86_64 dist-rocky8-compose sos
|
||||
|
||||
$ koji --quiet latest-build --arch=noarch dist-rocky8-compose sos
|
||||
sos-4.1-9.el8_5.rocky.3.noarch
|
||||
sos-audit-4.1-9.el8_5.rocky.3.noarch
|
||||
|
||||
$ dnf download --urls --repofrompath BaseOS,/media/BaseOS --repo BaseOS \
|
||||
--repofrompath Minimal,/media/Minimal --repo Minimal \
|
||||
sos sos-audit | grep -E "^file"
|
||||
file:///media/BaseOS/Packages/s/sos-4.1-5.el8.noarch.rpm
|
||||
file:///media/BaseOS/Packages/s/sos-audit-4.1-5.el8.noarch.rpm
|
||||
|
||||
$ rpm -q --changelog -p /media/BaseOS/Packages/s/sos-4.1-5.el8.noarch.rpm | \
|
||||
head | grep "Release Engineering <releng@rockylinux.org>" -C2
|
||||
$ echo $?
|
||||
1
|
||||
|
||||
$ rpm -q --changelog -p /media/BaseOS/Packages/s/sos-audit-4.1-5.el8.noarch.rpm | \
|
||||
head | grep "Release Engineering <releng@rockylinux.org>" -C2
|
||||
$ echo $?
|
||||
1
|
||||
|
||||
$ umount /media
|
||||
```
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
61
docs/documentation/QA/Testcase_Disk_Layouts.md
Normal file
61
docs/documentation/QA/Testcase_Disk_Layouts.md
Normal 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 'qa_data_loss_warning.md' %}
|
||||
|
||||
## Setup
|
||||
{% include '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 'qa_testcase_bottom.md' %}
|
||||
30
docs/documentation/QA/Testcase_Firmware_RAID.md
Normal file
30
docs/documentation/QA/Testcase_Firmware_RAID.md
Normal 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 'qa_testcase_bottom.md' %}
|
||||
55
docs/documentation/QA/Testcase_Installation_Interfaces.md
Normal file
55
docs/documentation/QA/Testcase_Installation_Interfaces.md
Normal 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 'qa_data_loss_warning.md' %}
|
||||
|
||||
## Setup
|
||||
{% include '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 'qa_testcase_bottom.md' %}
|
||||
46
docs/documentation/QA/Testcase_Installer_Help.md
Normal file
46
docs/documentation/QA/Testcase_Installer_Help.md
Normal 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 '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 'qa_testcase_bottom.md' %}
|
||||
37
docs/documentation/QA/Testcase_Installer_Translations.md
Normal file
37
docs/documentation/QA/Testcase_Installer_Translations.md
Normal 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 '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 'qa_testcase_bottom.md' %}
|
||||
41
docs/documentation/QA/Testcase_Kickstart_Installation.md
Normal file
41
docs/documentation/QA/Testcase_Kickstart_Installation.md
Normal 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 '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 '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://git.resf.org/testing/createhdds/raw/branch/rocky/server.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 'qa_testcase_bottom.md' %}
|
||||
175
docs/documentation/QA/Testcase_Media_File_Conflicts.md
Normal file
175
docs/documentation/QA/Testcase_Media_File_Conflicts.md
Normal file
@ -0,0 +1,175 @@
|
||||
---
|
||||
title: QA:Testcase Media File Conflicts
|
||||
author: Trevor Cooper
|
||||
revision_date: 2022-05-18
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver: 8
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#no-broken-packages](9_release_criteria.md#no-broken-packages) 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 testcase will verify that the offline repository included on release blocking images will not contain any file conflicts between packages without explicit `Conflicts:` tag in the package metadata.
|
||||
|
||||
## Setup
|
||||
1. Obtain access to an environment with the `dnf` and `python3` commands.
|
||||
2. Download the ISO to be tested to that machine.
|
||||
3. Download the `potential_conflict.py` script provided by Rocky Linux Testing Team.
|
||||
|
||||
## How to test
|
||||
1. Mount the ISO to be tested locally.
|
||||
- Example:<br>`mount -o loop Rocky-8.5-x86_64-minimal.iso /media`
|
||||
2. Determine the path to the `repodata` directory(ies) on the ISO.
|
||||
- Example:<br>`find /media -name repodata`
|
||||
3. Run the `potential_conflict.py` script on the mounted ISO.
|
||||
- Example:<br>`python3 /vagrant/scripts/potential_conflict.py --repofrompath BaseOS,/media/BaseOS --repoid BaseOS --repofrompath Minimal,/media/Minimal --repoid Minimal`
|
||||
4. Unmount the ISO.
|
||||
- Example:<br>`umount /media`
|
||||
|
||||
## Expected Results
|
||||
1. The `potential_conflict.py` script does not report any packages with non-declared conflicts.
|
||||
|
||||
<h3>Sample Output</h3>
|
||||
|
||||
=== "Success"
|
||||
|
||||
```
|
||||
$ sudo mount -o loop Rocky-8.5-aarch64-minimal.iso /media
|
||||
mount: /media: WARNING: device write-protected, mounted read-only.
|
||||
|
||||
$ python3 /vagrant/scripts/potential_conflict.py \
|
||||
--repofrompath BaseOS,/media/BaseOS --repoid BaseOS \
|
||||
--repofrompath Minimal,/media/Minimal --repoid Minimal
|
||||
|
||||
Added BaseOS repo from /media/BaseOS
|
||||
Added Minimal repo from /media/Minimal
|
||||
Getting complete filelist for:
|
||||
file:///media/BaseOS
|
||||
file:///media/Minimal
|
||||
168374 files found.
|
||||
|
||||
Looking for duplicated filenames:
|
||||
524 duplicates found.
|
||||
|
||||
Doing more advanced checks to see if these are real conflicts:
|
||||
10% complete ( 52/ 524, 1139/sec), 0 found - eta 0:00:00
|
||||
35% complete ( 182/ 524, 1146/sec), 0 found - eta 0:00:00
|
||||
45% complete ( 234/ 524, 1818/sec), 0 found - eta 0:00:00
|
||||
50% complete ( 260/ 524, 592673/sec), 0 found - eta 0:00:00
|
||||
55% complete ( 286/ 524, 778942/sec), 0 found - eta 0:00:00
|
||||
60% complete ( 312/ 524, 801852/sec), 0 found - eta 0:00:00
|
||||
79% complete ( 416/ 524, 234/sec), 0 found - eta 0:00:00
|
||||
84% complete ( 442/ 524, 902/sec), 0 found - eta 0:00:00
|
||||
89% complete ( 468/ 524, 935/sec), 0 found - eta 0:00:00
|
||||
94% complete ( 494/ 524, 1616/sec), 0 found - eta 0:00:00
|
||||
99% complete ( 520/ 524, 1114/sec), 0 found - eta 0:00:00
|
||||
|
||||
0 file conflicts found.
|
||||
0 package conflicts found.
|
||||
|
||||
== Package conflicts ==
|
||||
|
||||
== File conflicts, listed by conflicting packages ==
|
||||
|
||||
$ sudo umount /media
|
||||
```
|
||||
|
||||
=== "Failure"
|
||||
|
||||
```
|
||||
$ sudo mount -o loop Rocky-8.5-x86_64-dvd1.iso /media
|
||||
mount: /media: WARNING: device write-protected, mounted read-only.
|
||||
|
||||
|
||||
$ python3 /vagrant/scripts/potential_conflict.py \
|
||||
--repofrompath AppStream,/media/AppStream --repoid AppStream \
|
||||
--repofrompath BaseOS,/media/BaseOS --repoid BaseOS
|
||||
|
||||
Added AppStream repo from /media/AppStream
|
||||
Added BaseOS repo from /media/BaseOS
|
||||
Getting complete filelist for:
|
||||
file:///media/AppStream
|
||||
file:///media/BaseOS
|
||||
851967 files found.
|
||||
|
||||
Looking for duplicated filenames:
|
||||
101865 duplicates found.
|
||||
|
||||
Doing more advanced checks to see if these are real conflicts:
|
||||
5% complete ( 5093/101865, 8713/sec), 0 found - eta 0:00:11
|
||||
10% complete ( 10186/101865, 1787281/sec), 0 found - eta 0:00:05
|
||||
15% complete ( 15279/101865, 2223312/sec), 0 found - eta 0:00:03
|
||||
20% complete ( 20372/101865, 23614/sec), 0 found - eta 0:00:03
|
||||
25% complete ( 25465/101865, 57188/sec), 0 found - eta 0:00:02
|
||||
30% complete ( 30558/101865, 3831/sec), 0 found - eta 0:00:05
|
||||
35% complete ( 35651/101865, 48455/sec), 0 found - eta 0:00:04
|
||||
40% complete ( 40744/101865, 32067/sec), 0 found - eta 0:00:03
|
||||
45% complete ( 45837/101865, 2136586/sec), 0 found - eta 0:00:03
|
||||
50% complete ( 50930/101865, 72529/sec), 0 found - eta 0:00:02
|
||||
55% complete ( 56023/101865, 176294/sec), 0 found - eta 0:00:02
|
||||
60% complete ( 61116/101865, 68622/sec), 1 found - eta 0:00:01
|
||||
65% complete ( 66209/101865, 155133/sec), 1 found - eta 0:00:01
|
||||
70% complete ( 71302/101865, 13874/sec), 1 found - eta 0:00:01
|
||||
75% complete ( 76395/101865, 10835/sec), 1 found - eta 0:00:01
|
||||
80% complete ( 81488/101865, 27477/sec), 1 found - eta 0:00:00
|
||||
85% complete ( 86581/101865, 9075/sec), 1 found - eta 0:00:00
|
||||
90% complete ( 91674/101865, 14807/sec), 1 found - eta 0:00:00
|
||||
95% complete ( 96767/101865, 197437/sec), 1 found - eta 0:00:00
|
||||
100% complete (101860/101865, 38727/sec), 1 found - eta 0:00:00
|
||||
|
||||
1 file conflicts found.
|
||||
11 package conflicts found.
|
||||
|
||||
== Package conflicts ==
|
||||
mariadb-server-utils-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64
|
||||
mysql-server-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64
|
||||
|
||||
python3-mod_wsgi-4.6.4-4.el8.x86_64
|
||||
python38-mod_wsgi-4.6.8-3.module+el8.4.0+570+c2eaf144.x86_64
|
||||
python39-mod_wsgi-4.7.1-4.module+el8.4.0+574+843c4898.x86_64
|
||||
|
||||
libcmpiCppImpl0-2.0.3-15.el8.i686
|
||||
tog-pegasus-libs-2:2.14.1-46.el8.i686
|
||||
|
||||
mariadb-connector-c-devel-3.1.11-2.el8_3.i686
|
||||
mariadb-connector-c-devel-3.1.11-2.el8_3.x86_64
|
||||
mariadb-devel-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64
|
||||
mysql-devel-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64
|
||||
|
||||
mariadb-server-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64
|
||||
mysql-server-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64
|
||||
|
||||
mariadb-test-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64
|
||||
mysql-test-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64
|
||||
|
||||
mariadb-connector-c-devel-3.1.11-2.el8_3.i686
|
||||
mariadb-connector-c-devel-3.1.11-2.el8_3.x86_64
|
||||
mysql-devel-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64
|
||||
|
||||
mariadb-devel-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64
|
||||
mysql-devel-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64
|
||||
|
||||
mariadb-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64
|
||||
mysql-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64
|
||||
|
||||
libcmpiCppImpl0-2.0.3-15.el8.x86_64
|
||||
tog-pegasus-libs-2:2.14.1-46.el8.x86_64
|
||||
|
||||
libev-libevent-devel-4.24-6.el8.i686
|
||||
libev-libevent-devel-4.24-6.el8.x86_64
|
||||
libevent-devel-2.1.8-5.el8.i686
|
||||
libevent-devel-2.1.8-5.el8.x86_64
|
||||
|
||||
|
||||
== File conflicts, listed by conflicting packages ==
|
||||
mariadb-server-3:10.3.28-1.module+el8.4.0+427+adf35707.x86_64
|
||||
mysql-test-8.0.26-1.module+el8.4.0+652+6de068a7.x86_64
|
||||
/usr/bin/mysqld_safe
|
||||
|
||||
$ sudo umount /media
|
||||
```
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
86
docs/documentation/QA/Testcase_Media_Repoclosure.md
Normal file
86
docs/documentation/QA/Testcase_Media_Repoclosure.md
Normal file
@ -0,0 +1,86 @@
|
||||
---
|
||||
title: QA:Testcase Media Repoclosure
|
||||
author: Trevor Cooper
|
||||
revision_date: 2022-05-18
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver: 8
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#no-broken-packages](9_release_criteria.md#no-broken-packages) 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 testcase will verify that the offline repository included on release blocking images will not contain broken dependencies.
|
||||
|
||||
## Setup
|
||||
1. Obtain access to an environment with the `dnf repoclosure` command.
|
||||
2. Download the ISO to be tested to that machine.
|
||||
|
||||
## How to test
|
||||
1. Mount the ISO to be tested locally.
|
||||
- Example:<br>`mount -o loop Rocky-8.5-x86_64-minimal.iso /media`
|
||||
2. Determine the path to the `repodata` directory(ies) on the ISO.
|
||||
- Example:<br>`find /media -name repodata`
|
||||
3. Run the `dnf repoclosure` command on the mounted ISO.
|
||||
- Example:<br>`dnf --verbose repoclosure --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath Minimal,/media/Minimal --repo Minimal`
|
||||
4. Unmount the ISO.
|
||||
- Example:<br>`umount /media`
|
||||
|
||||
## Expected Results
|
||||
1. The `dnf repoclosure` command does not generate any errors.
|
||||
|
||||
<h3>Sample Output</h3>
|
||||
|
||||
=== "Success"
|
||||
|
||||
```
|
||||
$ sudo mount -o loop Rocky-8.5-x86_64-minimal.iso /media
|
||||
mount: /media: WARNING: device write-protected, mounted read-only.
|
||||
|
||||
[vagrant@localhost ~]$ dnf --refresh repoclosure \
|
||||
--repofrompath BaseOS,/media/BaseOS --repo BaseOS \
|
||||
--repofrompath Minimal,/media/Minimal --repo Minimal
|
||||
Added BaseOS repo from /media/BaseOS
|
||||
Added Minimal repo from /media/Minimal
|
||||
BaseOS 102 MB/s | 2.6 MB 00:00
|
||||
Minimal 90 kB/s | 384 B 00:00
|
||||
|
||||
$ sudo umount /media
|
||||
```
|
||||
|
||||
=== "Failure"
|
||||
|
||||
__NOTE: In this example the content of the `Rocky-8.5-x86_64-minimal.iso` was copied to `/tmp` then the BaseOS repository was modified to remove the `setup-2.12.2-6.el8.noarch.rpm` package and the repository metadata was regenerated.__
|
||||
|
||||
```
|
||||
[vagrant@localhost ~]$ dnf --refresh repoclosure \
|
||||
--repofrompath BaseOS,/tmp/media/BaseOS --repo BaseOS \
|
||||
--repofrompath Minimal,/tmp/media/Minimal --repo Minimal
|
||||
Added BaseOS repo from /tmp/media/BaseOS
|
||||
Added Minimal repo from /tmp/media/Minimal
|
||||
BaseOS 3.7 MB/s | 3.8 kB 00:00
|
||||
Minimal 3.7 MB/s | 3.8 kB 00:00
|
||||
package: basesystem-11-5.el8.noarch from BaseOS
|
||||
unresolved deps:
|
||||
setup
|
||||
package: dump-1:0.4-0.36.b46.el8.x86_64 from BaseOS
|
||||
unresolved deps:
|
||||
setup
|
||||
package: filesystem-3.8-6.el8.x86_64 from BaseOS
|
||||
unresolved deps:
|
||||
setup
|
||||
package: initscripts-10.00.15-1.el8.x86_64 from BaseOS
|
||||
unresolved deps:
|
||||
setup
|
||||
package: rpcbind-1.2.5-8.el8.x86_64 from BaseOS
|
||||
unresolved deps:
|
||||
setup
|
||||
package: shadow-utils-2:4.6-14.el8.x86_64 from BaseOS
|
||||
unresolved deps:
|
||||
setup
|
||||
Error: Repoclosure ended with unresolved dependencies.
|
||||
```
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
61
docs/documentation/QA/Testcase_Media_USB_dd.md
Normal file
61
docs/documentation/QA/Testcase_Media_USB_dd.md
Normal file
@ -0,0 +1,61 @@
|
||||
---
|
||||
title: QA:Testcase Media USB dd
|
||||
author: Trevor Cooper
|
||||
revision_date: 2022-05-18
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver: 8
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#initialization-requirements](9_release_criteria.md#initialization-requirements) 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 verifies that Rocky Linux ISO image can be written to USB media using `dd` command, and the resulting USB media successfully boots to the Anaconda Installer.
|
||||
|
||||
!!! error "DATA LOSS"
|
||||
Any data on the USB stick used for this test is likely to be destroyed. Please do not use a stick whose contents you need to keep.
|
||||
|
||||
## Setup
|
||||
|
||||
1. Provide a USB media device that is larger than the ISO image you wish to test and that it can be completely erased.
|
||||
2. Provide a Linux (or other *nix system) that has the `dd` command available and an unoccupied USB port.
|
||||
3. Download the Rocky Linux ISO image you wish to test onto the test system.
|
||||
- Example command:<br>`curl -LOR https://dl.rockylinux.org/pub/rocky/8/isos/x86_64/Rocky-x86_64-boot.iso`
|
||||
4. Download the `CHECKSUM` file that goes with the Rocky Linux ISO image that you wish to test.
|
||||
- Example command:<br>`curl -LOR https://dl.rockylinux.org/pub/rocky/8/isos/x86_64/CHECKSUM`
|
||||
5. Download the `CHECKSUM.sig` file that does with the `CHECKSUM` file.
|
||||
- Example command:<br>`curl -LOR https://dl.rockylinux.org/pub/rocky/8/isos/x86_64/CHECKSUM.sig`
|
||||
6. Download the Rocky Release Engineering GPG key.
|
||||
- Example command:<br>`curl -LOR https://dl.rockylinux.org/pub/rocky/RPM-GPG-KEY-rockyofficial`
|
||||
|
||||
## How to test
|
||||
|
||||
1. Import the Rocky Release Engineering GPG key.
|
||||
- Example command:<br>`gpg --import RPM-GPG-KEY-rockyofficial`
|
||||
2. Verify the signature of the CHECKSUM file.
|
||||
- Example command:<br>`gpg --verify-file CHECKSUM.sig`
|
||||
3. Verify the CHECKSUM of the Rocky Linux ISO...
|
||||
- Example command:<br>`shasum -a 256 --ignore-missing -c CHECKSUM`
|
||||
4. Write the Rocky Linux ISO to the USB media using `dd`...
|
||||
- Example command:<br>`dd if=Rocky-8.5-x86_64-boot.iso of=/dev/sdX bs=16M status=progress oflag=direct`<br>...where you replace `sdX` with the device identifier of your USB media.<br>**This will destroy all data on the disk.**
|
||||
5. Boot the test system with the USB media.
|
||||
6. In the boot menu select the appropriate option to boot the installer.
|
||||
7. **[OPTIONAL]** Proceed with installation on the test system.<br>**Depending on installer choices this MAY destroy all the data on the test system.**
|
||||
|
||||
## Expected Results
|
||||
|
||||
1. The gpg signature on the `CHECKSUM` file is valid.
|
||||
2. The `CHECKSUM` of the Rocky Linux ISO is valid.
|
||||
3. The Rocky Linux ISO is written to the USB stick without errors.
|
||||
4. The USB stick boots without errors.
|
||||
5. The Anaconda Installer starts without errors.
|
||||
|
||||
!!! error "DATA LOSS"
|
||||
If you choose to complete the installation of the test system any/all data on the system may be lost. Please do not install on a system whose contents you need to keep.
|
||||
|
||||
**[OPTIONALLY]**<br>
|
||||
6. The installation finishes successfully and, if the minimal or DVD ISO were used, the package repository on the USB stick (not a network based repository) was used for the installation.
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
37
docs/documentation/QA/Testcase_Minimal_Installation.md
Normal file
37
docs/documentation/QA/Testcase_Minimal_Installation.md
Normal 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 'qa_data_loss_warning.md' %}
|
||||
|
||||
## Setup
|
||||
{% include '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 'qa_testcase_bottom.md' %}
|
||||
37
docs/documentation/QA/Testcase_Network_Attached_Storage.md
Normal file
37
docs/documentation/QA/Testcase_Network_Attached_Storage.md
Normal 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 'qa_testcase_bottom.md' %}
|
||||
53
docs/documentation/QA/Testcase_Packages_Installer_Sources.md
Normal file
53
docs/documentation/QA/Testcase_Packages_Installer_Sources.md
Normal 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 'qa_data_loss_warning.md' %}
|
||||
|
||||
## Setup
|
||||
{% include '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 'qa_testcase_bottom.md' %}
|
||||
96
docs/documentation/QA/Testcase_Packages_No_Insights.md
Normal file
96
docs/documentation/QA/Testcase_Packages_No_Insights.md
Normal file
@ -0,0 +1,96 @@
|
||||
---
|
||||
title: QA:Testcase Packages No Insights
|
||||
author: Trevor Cooper
|
||||
revision_date: 2022-05-18
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver: 8
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#repositories-must-match-upstream](9_release_criteria.md#repositories-must-match-upstream) 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 will verify that `insights-client` package is not declared be installed as part of a package group.
|
||||
|
||||
## Setup
|
||||
1. Obtain access to an environment with the `dnf` command.
|
||||
2. Download the ISO to be tested to that machine.
|
||||
|
||||
## How to test
|
||||
1. Mount the ISO to be tested locally.
|
||||
2. Determine the path to the `comps` file(s) on the ISO.
|
||||
3. Verify that `insights-client` is not declared to be installed automatically.
|
||||
- Example 1:<br>`find /media -name "*comps*.xml" -exec grep -H "insights-client" '{}' \;`
|
||||
- Example 2:<br>`dnf --refresh --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath AppStream,/media/AppStream --repo AppStream groupinfo base | grep -E ":|insights"`
|
||||
4. Unmount the ISO.
|
||||
|
||||
## Expected Results
|
||||
1. `insights-client` is not declared to be installed by default.
|
||||
|
||||
<h3>Sample Output</h3>
|
||||
|
||||
=== "Success"
|
||||
|
||||
|
||||
!!! info "UPDATE SAMPLE"
|
||||
NOTE: This example needs to be refreshed when the 8.6 ISO has been produced. As seen in the Failure section below the `Rocky-8.5-x86_64-dvd1.iso` includes the `insights-client` as part of the `base` group. The package should be included on the DVD ISO but should **not** be installed automatically.
|
||||
|
||||
```
|
||||
$ sudo mount -o loop Rocky-8.5-aarch64-minimal.iso /media
|
||||
mount: /media: WARNING: device write-protected, mounted read-only.
|
||||
|
||||
$ dnf --refresh --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath Minimal,/media/Minimal --repo Minimal search insights-client
|
||||
Added BaseOS repo from /media/BaseOS
|
||||
Added Minimal repo from /media/Minimal
|
||||
BaseOS 3.8 MB/s | 3.9 kB 00:00
|
||||
Minimal 3.7 MB/s | 3.8 kB 00:00
|
||||
No matches found.
|
||||
|
||||
$ find /media -name "*comps*.xml" -exec grep -H "insights-client" '{}' \;
|
||||
|
||||
$ dnf --refresh --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath Minimal,/media/Minimal --repo Minimal groupinfo base | grep -E ":|insights"
|
||||
BaseOS 3.8 MB/s | 3.9 kB 00:00
|
||||
Minimal 3.7 MB/s | 3.8 kB 00:00
|
||||
Group: Base
|
||||
Description: The standard installation of Rocky Linux.
|
||||
Mandatory Packages:
|
||||
Default Packages:
|
||||
Optional Packages:
|
||||
|
||||
$ sudo umount /media
|
||||
```
|
||||
|
||||
=== "Failure"
|
||||
|
||||
```
|
||||
$ sudo mount -o loop Rocky-8.5-x86_64-dvd1.iso /media
|
||||
mount: /media: WARNING: device write-protected, mounted read-only.
|
||||
|
||||
$ dnf --refresh --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath AppStream,/media/AppStream --repo AppStream search insights-client
|
||||
Added BaseOS repo from /media/BaseOS
|
||||
Added AppStream repo from /media/AppStream
|
||||
BaseOS 3.8 MB/s | 3.9 kB 00:00
|
||||
AppStream 4.2 MB/s | 4.3 kB 00:00
|
||||
================================= Name Exactly Matched: insights-client ==================================
|
||||
insights-client.noarch : Uploads Insights information to Red Hat on a periodic basis
|
||||
|
||||
$ find /media -name "*comps*.xml" -exec grep -H "insights-client" '{}' \;
|
||||
/media/AppStream/repodata/a6742e1300e1c786af91656b152d3b98bb7aff598e650509381417970e1f1b7e-comps-AppStream.x86_64.xml: <packagereq type="default">insights-client</packagereq>
|
||||
/media/AppStream/repodata/a6742e1300e1c786af91656b152d3b98bb7aff598e650509381417970e1f1b7e-comps-AppStream.x86_64.xml: <packagereq type="default">insights-client</packagereq>
|
||||
|
||||
$ dnf --refresh --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath AppStream,/media/AppStream --repo AppStream groupinfo base | grep -E ":|insights"
|
||||
BaseOS 3.8 MB/s | 3.9 kB 00:00
|
||||
AppStream 4.2 MB/s | 4.3 kB 00:00
|
||||
Group: Base
|
||||
Description: The standard installation of Rocky Linux.
|
||||
Mandatory Packages:
|
||||
Default Packages:
|
||||
insights-client
|
||||
Optional Packages:
|
||||
|
||||
$ sudo umount /media
|
||||
```
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
63
docs/documentation/QA/Testcase_Packages_No_RHSM.md
Normal file
63
docs/documentation/QA/Testcase_Packages_No_RHSM.md
Normal file
@ -0,0 +1,63 @@
|
||||
---
|
||||
title: QA:Testcase Packages No RHSM
|
||||
author: Trevor Cooper
|
||||
revision_date: 2022-05-18
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver: 8
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#repositories-must-match-upstream](9_release_criteria.md#repositories-must-match-upstream) 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 will verify that packages that are availble from upstream do not have hard requirements on `subscription-manager` (RHSM).
|
||||
|
||||
## Setup
|
||||
1. Obtain access to an environment with the `dnf` command.
|
||||
2. Download the ISO to be tested to that machine.
|
||||
|
||||
## How to test
|
||||
1. Mount the ISO to be tested locally.
|
||||
2. Obtain a list of packages that have `Requires:` for `subscription-manager`
|
||||
- Example:<br>`package_list=($(dnf --refresh repoquery --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath AppStream,/media/AppStream --repo AppStream --whatrequires subscription-manager 2>/dev/null| grep el8))`
|
||||
3. Download the packages with explicity `Requires:` for `subscription-manager`
|
||||
- Example:<br>`dnf --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath AppStream,/media/AppStream --repo AppStream download "${package_list[@]}"`
|
||||
4. Obtain the `SOURCEPKG` definition for the above packages
|
||||
- Example:<br>`rpm -q --queryformat="%{NAME}|%{SOURCERPM}\n" subscription-manager*.rpm | column -s\| -t`
|
||||
4. Unmount the ISO.
|
||||
|
||||
## Expected Results
|
||||
1. No packages have an explicit requirement for `subscription-manager`.
|
||||
|
||||
|
||||
<h3>Sample Output</h3>
|
||||
|
||||
=== "Success"
|
||||
|
||||
```
|
||||
$ sudo mount -o loop Rocky-8.5-aarch64-minimal.iso /media
|
||||
mount: /media: WARNING: device write-protected, mounted read-only.
|
||||
|
||||
$ package_list=($(dnf --refresh repoquery --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath AppStream,/media/AppStream --repo AppStream --whatrequires subscription-manager 2>/dev/null| grep el8))
|
||||
|
||||
$ dnf --repofrompath BaseOS,/media/BaseOS --repo BaseOS --repofrompath AppStream,/media/AppStream --repo AppStream download "${package_list[@]}"
|
||||
Added BaseOS repo from /media/BaseOS
|
||||
Added AppStream repo from /media/AppStream
|
||||
Last metadata expiration check: 0:00:25 ago on Sun 24 Apr 2022 10:57:13 PM UTC.
|
||||
|
||||
$ rpm -q --queryformat="%{NAME}|%{SOURCERPM}\n" subscription-manager*.rpm | column -s\| -t
|
||||
subscription-manager-cockpit subscription-manager-1.28.21-3.el8.src.rpm
|
||||
subscription-manager-migration subscription-manager-1.28.21-3.el8.src.rpm
|
||||
subscription-manager-plugin-ostree subscription-manager-1.28.21-3.el8.src.rpm
|
||||
|
||||
$ sudo umount /media
|
||||
```
|
||||
|
||||
=== "Failure"
|
||||
|
||||
TBD
|
||||
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
@ -0,0 +1,55 @@
|
||||
---
|
||||
title: QA:Testcase Application Functionality
|
||||
author: Lukas Magauer
|
||||
revision_date: 2022-05-31
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver:
|
||||
- 8
|
||||
- 9
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Release relevance"
|
||||
This Testcase applies the following versions of {{ rc.prod }}: {% for version in rc.ver %}{{ version }}{% if not loop.last %}, {% endif %}{% endfor %}
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#default-application-functionality-desktop-only](9_release_criteria.md#default-application-functionality-desktop-only) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
|
||||
|
||||
!!! error "REFERENCED RELEASE CRITERIA IS OVERLY GENERAL AND UNTESTABLE"
|
||||
The associated release criteria, [Release_Criteria#default-application-functionality-desktop-only](9_release_criteria.md#default-application-functionality-desktop-only), for this test case is overly general and **must** be modified to specific enough to be testable.
|
||||
|
||||
## Description
|
||||
|
||||
This testcase handles all applications, considered as core applications of the desktop environment GNOME or user facing commandline applications.
|
||||
|
||||
The following tasks apply in general to all of the following applications:
|
||||
|
||||
- Firefox
|
||||
- Files (Nautilus)
|
||||
- GNOME Software
|
||||
- (Image Viewer)
|
||||
- (Document Viewer)
|
||||
- Gedit (Text Editor)
|
||||
- Archive Manager
|
||||
- GNOME Terminal (Terminal Emulator)
|
||||
- Problem Reporter
|
||||
- Help Viewer
|
||||
- System Settings
|
||||
- vim (Console Text Editor)
|
||||
|
||||
## Setup
|
||||
|
||||
Obtain access to a suitable system with either a Workstation or a Graphical Server installation.
|
||||
|
||||
## How to test
|
||||
|
||||
1. Check that the application starts without any errors
|
||||
2. Further check that the context menus for the correct function
|
||||
3. Open files to test the functionality of the individual applications
|
||||
|
||||
## Expected Results
|
||||
|
||||
Make sure that the individual applications behave as they should.
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
44
docs/documentation/QA/Testcase_Post_Artwork_and_Assets.md
Normal file
44
docs/documentation/QA/Testcase_Post_Artwork_and_Assets.md
Normal file
@ -0,0 +1,44 @@
|
||||
---
|
||||
title: QA:Testcase Artwork and Assets
|
||||
author: Lukas Magauer
|
||||
revision_date: 2022-05-31
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver:
|
||||
- 8
|
||||
- 9
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Release relevance"
|
||||
This Testcase applies the following versions of {{ rc.prod }}: {% for version in rc.ver %}{{ version }}{% if not loop.last %}, {% endif %}{% endfor %}
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#artwork-and-assets-server-and-desktop](9_release_criteria.md#artwork-and-assets-server-and-desktop) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
|
||||
|
||||
## Description
|
||||
|
||||
There are several brand artworks and assets throughout the whole OS, this testcase will take care of checking, that these are actually in place, and don't produce any UI errors. This is exclusively for installations with the default desktop environment GDM and GNOME.
|
||||
|
||||
## Setup
|
||||
|
||||
1. Acquire access to either a baremetal machine or a VM host, to install a new machine
|
||||
2. Prepare appropriate media for the selected ISO to be tested.
|
||||
- Example: [QA:Testcase Media USB dd](Testcase_Media_USB_dd.md)
|
||||
|
||||
## How to test
|
||||
|
||||
1. While booting the image check, that the correct logo is visible in the loading screen before Anaconda comes up
|
||||
2. Look at the Anaconda images in the [rocky-logos repo](https://github.com/rocky-linux/rocky-logos/tree/r8-fedora/anaconda) and check if all assets are correctly applied in Anaconda (they will generally be visible right away while going through the install process)
|
||||
3. Install the system with either the Workstation install set or Graphical Server
|
||||
4. While the OS does its first boot, check that the correct logo is visible in the loading screen before the boot login screen shows up
|
||||
5. Check the logo and background of the boot login screen
|
||||
6. After the login check the desktop background and further all available options in the settings menu for the desktop background
|
||||
7. Lock the screen and check the background visible in the flyover
|
||||
8. At last check the logo and background of the login screen
|
||||
|
||||
## Expected Results
|
||||
|
||||
The tests during the process could be successfully finished.
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
@ -0,0 +1,45 @@
|
||||
---
|
||||
title: QA:Testcase GNOME UI Functionality
|
||||
author: Lukas Magauer
|
||||
revision_date: 2022-05-31
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver:
|
||||
- 8
|
||||
- 9
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Release relevance"
|
||||
This Testcase applies the following versions of {{ rc.prod }}: {% for version in rc.ver %}{{ version }}{% if not loop.last %}, {% endif %}{% endfor %}
|
||||
|
||||
!!! error "REFERENCED RELEASE CRITERIA IS OVERLY GENERAL AND UNTESTABLE"
|
||||
The associated release criteria, [Release_Criteria#default-panel-functionality-desktop-only](9_release_criteria.md#default-panel-functionality-desktop-only), for this test case is overly general and **must** be modified to specific enough to be testable.
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#default-panel-functionality-desktop-only](9_release_criteria.md#default-panel-functionality-desktop-only) 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 collection takes care of the correct functionality of the GNOME UI.
|
||||
|
||||
## Setup
|
||||
|
||||
Obtain access to a suitable system with either a Workstation or a Graphical Server installation.
|
||||
|
||||
## How to test
|
||||
|
||||
1. Login to the Rocky Machine via the UI
|
||||
2. Navigate through the GNOME UI
|
||||
|
||||
## Expected Results
|
||||
|
||||
1. After the login you should have landed on the desktop with the background and the top bar of GNOME visible
|
||||
2. Clicking the the Activities button in the upper right should bring up the overview
|
||||
3. Further there should be the favourite applications ribbon on the left
|
||||
4. And after clicking the 9-dot-icon all applications should appear
|
||||
5. Back on the desktop check the function of the system and clock panel on the upper right and middle
|
||||
|
||||
It is also a good measure to do some more basic clicking through the GNOME UI, like opening applications, interacting with the application headerbar, moving applications to different desktops or changing settings in the System settings.
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
68
docs/documentation/QA/Testcase_Post_Identity_Management.md
Normal file
68
docs/documentation/QA/Testcase_Post_Identity_Management.md
Normal file
@ -0,0 +1,68 @@
|
||||
---
|
||||
title: QA:Testcase Identity Management
|
||||
author: Lukas Magauer
|
||||
revision_date: 2022-10-08
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver:
|
||||
- 8
|
||||
- 9
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Release relevance"
|
||||
This Testcase applies the following versions of {{ rc.prod }}: {% for version in rc.ver %}{{ version }}{% if not loop.last %}, {% endif %}{% endfor %}
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#packages-and-module-installation](9_release_criteria.md#packages-and-module-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
|
||||
|
||||
Setting up a IdM system (FreeIPA) and using it's functionality leverages not also a lot of the packages in the official repos, it also tests quite a lot of used functions a corporate environment. This installatation will host it's own dns server for more generic testing without relying on the individual infrastructure of the environment.
|
||||
|
||||
## Requirements
|
||||
|
||||
- A freshly provisioned system (no other functions are allowed on this system except running the IdM services)
|
||||
- IPv4 network with unmanaged domain name (installer will check for dns servers) and unmanaged reverse dns network (in my case here 10.30.30.0/24 and ipa1.network)
|
||||
- In the case of this writeup the external dns server has the domain `example.com`, this has to have a entry for `r8-ipa1-dev.example.com` (this could also be replaced by a entry in the `/etc/hosts` file if no external dns server should be involved)
|
||||
|
||||
## Setup
|
||||
|
||||
1. `dnf module enable idm:DL1`
|
||||
2. `dnf module install idm:DL1/dns`
|
||||
3. `ipa-server-install`
|
||||
|
||||
- Do you want to configure integrated DNS (BIND)? [no]: yes
|
||||
- Server host name [r8-ipa1-dev.example.com]: r8-ipa1-dev.example.com
|
||||
- Please confirm the domain name [ipa1.network]: ipa1.network
|
||||
- Please provide a realm name [IPA1.NETWORK]: IPA1.NETWORK
|
||||
- Directory Manager password: `<password>`
|
||||
Password (confirm): `<password>`
|
||||
- IPA admin password: `<other-password>`
|
||||
Password (confirm): `<other-password>`
|
||||
- Please provide the IP address to be used for this host name: 10.30.30.1
|
||||
- Enter an additional IP address, or press Enter to skip: `leave empty`
|
||||
- Do you want to configure DNS forwarders? [yes]: yes
|
||||
- Do you want to configure these servers as DNS forwarders? [yes]: yes
|
||||
- Enter an IP address for a DNS forwarder, or press Enter to skip: `leave empty`
|
||||
- Do you want to search for missing reverse zones? [yes]: yes
|
||||
- NetBIOS domain name [IPA1]: IPA1
|
||||
- Do you want to configure chrony with NTP server or pool address? [no]: yes
|
||||
- Enter NTP source server addresses separated by comma, or press Enter to skip: `leave empty`
|
||||
- Enter a NTP source pool address, or press Enter to skip: pool.ntp.org
|
||||
- Continue to configure the system with these values? [no]: yes
|
||||
|
||||
4. `firewall-cmd --add-service={freeipa-4,dns} --permanent`
|
||||
5. `firewall-cmd --add-service={freeipa-4,dns}`
|
||||
|
||||
## How to test
|
||||
|
||||
1. Make sure Kerberos works, by running `kinit admin` and `klist`
|
||||
2. Make sure the webfrontend is reachable and login works
|
||||
3. Furthermore you can also attach another system (DNS + connecting via SSSD)
|
||||
|
||||
## Expected Results
|
||||
|
||||
After installation all services should be available and work correctly.
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
60
docs/documentation/QA/Testcase_Post_Keyboard_Layout.md
Normal file
60
docs/documentation/QA/Testcase_Post_Keyboard_Layout.md
Normal file
@ -0,0 +1,60 @@
|
||||
---
|
||||
title: QA:Testcase Keyboard Layout
|
||||
author: Lukas Magauer
|
||||
revision_date: 2022-05-31
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver:
|
||||
- 8
|
||||
- 9
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Release relevance"
|
||||
This Testcase applies the following versions of {{ rc.prod }}: {% for version in rc.ver %}{{ version }}{% if not loop.last %}, {% endif %}{% endfor %}
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#keyboard-layout](9_release_criteria.md#keyboard-layout) release criterion. If you are doing release validation testing, a failure of this test case may be a breach of that release criterion.
|
||||
|
||||
## Description
|
||||
|
||||
As there are a lot of different keyboard layouts available, it is necessary to test if the keyboard functionality works without any issues throughout the system.
|
||||
|
||||
## Setup
|
||||
|
||||
- Obtain access to a few different system configurations, especially with and without UI, and not to forget with disk encryption.
|
||||
- Acquire access to either a baremetal machine or a VM host, to install a new machine
|
||||
- Prepare appropriate media for the selected ISO to be tested.
|
||||
- Example: [QA:Testcase Media USB dd](Testcase_Media_USB_dd.md)
|
||||
|
||||
## How to test
|
||||
|
||||
### Installer
|
||||
|
||||
1. Bootup the installer
|
||||
2. Choose a language
|
||||
3. Make sure that the keyboard layout got chosen correctly corresponding to the language setting
|
||||
4. Change the keyboard layout if needed to test
|
||||
5. Enter text all over Anaconda to make sure the keyboard layout works correctly with the chosen keyboard layout
|
||||
|
||||
### Disk Encryption
|
||||
|
||||
1. Setup a system with disk encryption
|
||||
2. Check that the password for the disk encryption works on bootup with graphical UI
|
||||
3. Check that the password for the disk encryption works on bootup with text mode
|
||||
|
||||
### Text mode
|
||||
|
||||
Check that the chosen keyboard layout works correctly on text mode.
|
||||
|
||||
### GNOME and Application
|
||||
|
||||
1. Check the login, that the keyboard layout works correctly on the graphical UI login screen
|
||||
2. Also check that the GNOME UI works correctly with the chosen keyboard layout
|
||||
3. And finally check some applications, that the keyboard works as expected
|
||||
|
||||
## Expected Results
|
||||
|
||||
The tests during the process could be successfully finished.
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
49
docs/documentation/QA/Testcase_Post_Module_Streams.md
Normal file
49
docs/documentation/QA/Testcase_Post_Module_Streams.md
Normal file
@ -0,0 +1,49 @@
|
||||
---
|
||||
title: QA:Testcase Module Streams
|
||||
author: Lukas Magauer
|
||||
revision_date: 2022-05-31
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver:
|
||||
- 8
|
||||
- 9
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Release relevance"
|
||||
This Testcase applies the following versions of {{ rc.prod }}: {% for version in rc.ver %}{{ version }}{% if not loop.last %}, {% endif %}{% endfor %}
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#packages-and-module-installation](9_release_criteria.md#packages-and-module-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 takes care of testing the module streams, that they are all installable, all available and working as expected.
|
||||
|
||||
## Setup
|
||||
|
||||
For this tests you will need to install every module stream on its own, so it's the best to setup a new system which gets snapshoted after the initial setup. After that it can be rolled back for every module install.
|
||||
|
||||
It's enough to setup a system with the Minimal Install group.
|
||||
|
||||
## How to test
|
||||
|
||||
1. Login to the machine
|
||||
2. Get a list of all module streams and compare it to the [stream list from RHEL](https://access.redhat.com/support/policy/updates/rhel-app-streams-life-cycle) and to the source in [Git source repo](https://git.rockylinux.org/rocky/rocky-module-defaults)
|
||||
3. The easiest way to test all streams is to install the package groups in the individual streams, i.e. for postgresql:
|
||||
|
||||
```bash
|
||||
dnf module install postgresql
|
||||
dnf module install postgresql:13
|
||||
dnf module install postgresql:13/client
|
||||
```
|
||||
|
||||
Repeat step 3 as often as module streams and package groups are available.
|
||||
|
||||
This could be automated with i.e. Ansible to do all the `install -> rollback -> install -> rollback -> ...` and emiting the output via Ansible.
|
||||
|
||||
## Expected Results
|
||||
|
||||
All module streams should be available and there shouldn't be any errors while installing any of the package groups of the individual streams. (some of the installs will show warnings though because they are incompatible with other streams)
|
||||
|
||||
{% include 'qa_testcase_bottom.md' %}
|
||||
36
docs/documentation/QA/Testcase_Post_Multimonitor_Setup.md
Normal file
36
docs/documentation/QA/Testcase_Post_Multimonitor_Setup.md
Normal file
@ -0,0 +1,36 @@
|
||||
---
|
||||
title: QA:Testcase Multimonitor Setup
|
||||
author: Lukas Magauer
|
||||
revision_date: 2022-05-31
|
||||
rc:
|
||||
prod: Rocky Linux
|
||||
ver:
|
||||
- 8
|
||||
- 9
|
||||
level: Final
|
||||
---
|
||||
|
||||
!!! info "Release relevance"
|
||||
This Testcase applies the following versions of {{ rc.prod }}: {% for version in rc.ver %}{{ version }}{% if not loop.last %}, {% endif %}{% endfor %}
|
||||
|
||||
!!! info "Associated release criterion"
|
||||
This test case is associated with the [Release_Criteria#dual-monitor-setup-desktop-only](9_release_criteria.md#dual-monitor-setup-desktop-only) 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 covers the check if GNOME behaves as it should in multi-monitor setups.
|
||||
|
||||
## Setup
|
||||
|
||||
You will need either a machine which can be reinstalled with multiple screens, or a virtualization software which is capable of providing multiple screens (like VMware Workstation ([Pro](https://www.vmware.com/products/workstation-pro/workstation-pro-evaluation.html) or [Player](https://www.vmware.com/products/workstation-player/workstation-player-evaluation.html)) or [VMware Fusion](https://www.vmware.com/products/fusion/fusion-evaluation.html), but there is also a [hack](https://communities.vmware.com/t5/VMware-vSphere-Discussions/ESXi-6-7-Multiple-Monitors-for-VMs/td-p/2748906) for [VMware ESXi](https://customerconnect.vmware.com/en/web/vmware/evalcenter?p=vsphere-eval-7))
|
||||
|
||||
## How to test
|
||||
|
||||