From 483766fd50994106f5ddfd2a6c86460b8506c142 Mon Sep 17 00:00:00 2001 From: Trevor Cooper Date: Sun, 21 Apr 2024 13:46:20 -0700 Subject: [PATCH] update include path --- docs/documentation/QA/Testcase_Basic_Graphics_Mode.md | 4 ++-- docs/documentation/QA/Testcase_Boot_Methods_Boot_Iso.md | 2 +- docs/documentation/QA/Testcase_Boot_Methods_Dvd.md | 2 +- docs/documentation/QA/Testcase_Bootloader_Disk_Selection.md | 6 +++--- .../QA/Testcase_Custom_Boot_Methods_Boot_Iso.md | 2 +- docs/documentation/QA/Testcase_Debranding.md | 2 +- docs/documentation/QA/Testcase_Disk_Layouts.md | 6 +++--- docs/documentation/QA/Testcase_Firmware_RAID.md | 2 +- docs/documentation/QA/Testcase_Installation_Interfaces.md | 6 +++--- docs/documentation/QA/Testcase_Installer_Help.md | 4 ++-- docs/documentation/QA/Testcase_Installer_Translations.md | 4 ++-- docs/documentation/QA/Testcase_Kickstart_Installation.md | 6 +++--- docs/documentation/QA/Testcase_Media_File_Conflicts.md | 2 +- docs/documentation/QA/Testcase_Media_Repoclosure.md | 2 +- docs/documentation/QA/Testcase_Media_USB_dd.md | 2 +- docs/documentation/QA/Testcase_Minimal_Installation.md | 6 +++--- docs/documentation/QA/Testcase_Network_Attached_Storage.md | 2 +- .../documentation/QA/Testcase_Packages_Installer_Sources.md | 6 +++--- docs/documentation/QA/Testcase_Packages_No_Insights.md | 2 +- docs/documentation/QA/Testcase_Packages_No_RHSM.md | 2 +- .../QA/Testcase_Post_Application_Functionality.md | 2 +- docs/documentation/QA/Testcase_Post_Artwork_and_Assets.md | 2 +- .../QA/Testcase_Post_GNOME_UI_Functionality.md | 2 +- docs/documentation/QA/Testcase_Post_Identity_Management.md | 2 +- docs/documentation/QA/Testcase_Post_Keyboard_Layout.md | 2 +- docs/documentation/QA/Testcase_Post_Module_Streams.md | 2 +- docs/documentation/QA/Testcase_Post_Multimonitor_Setup.md | 2 +- docs/documentation/QA/Testcase_Post_Package_installs.md | 2 +- .../QA/Testcase_Post_SELinux_Errors_Desktop.md | 2 +- .../documentation/QA/Testcase_Post_SELinux_Errors_Server.md | 2 +- docs/documentation/QA/Testcase_Post_System_Services.md | 2 +- docs/documentation/QA/Testcase_Repo_Compare.md | 2 +- docs/documentation/QA/Testcase_Storage_Volume_Resize.md | 6 +++--- docs/documentation/QA/Testcase_Template.md | 2 +- docs/documentation/QA/Testcase_Update_Image.md | 6 +++--- docs/documentation/QA/Testcase_VNC_Graphics_Mode.md | 4 ++-- docs/documentation/dev_guides/wiki_development_boxes.md | 2 +- docs/guidelines/release_criteria/r8/8_release_criteria.md | 2 +- docs/guidelines/release_criteria/r9/9_release_criteria.md | 2 +- 39 files changed, 59 insertions(+), 59 deletions(-) diff --git a/docs/documentation/QA/Testcase_Basic_Graphics_Mode.md b/docs/documentation/QA/Testcase_Basic_Graphics_Mode.md index 15499d1..0658ab0 100644 --- a/docs/documentation/QA/Testcase_Basic_Graphics_Mode.md +++ b/docs/documentation/QA/Testcase_Basic_Graphics_Mode.md @@ -17,7 +17,7 @@ rc: ## 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 'testing/qa_testcase_supported_systems.md' %} +{% include 'qa_testcase_supported_systems.md' %} ## Setup 1. Obtain access to supported system and hardware class to be installed. @@ -41,4 +41,4 @@ This test case will verify that release-blocking installers function as intended 4. After reboot system boots into graphical environment. 5. After login user is able to operate the graphical environment. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Boot_Methods_Boot_Iso.md b/docs/documentation/QA/Testcase_Boot_Methods_Boot_Iso.md index 77441ab..77f90f8 100644 --- a/docs/documentation/QA/Testcase_Boot_Methods_Boot_Iso.md +++ b/docs/documentation/QA/Testcase_Boot_Methods_Boot_Iso.md @@ -25,4 +25,4 @@ This is to verify that the Anaconda installer starts correctly when booting from 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 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Boot_Methods_Dvd.md b/docs/documentation/QA/Testcase_Boot_Methods_Dvd.md index f242746..f979aa7 100644 --- a/docs/documentation/QA/Testcase_Boot_Methods_Dvd.md +++ b/docs/documentation/QA/Testcase_Boot_Methods_Dvd.md @@ -25,4 +25,4 @@ This is to verify that the Anaconda installer starts correctly when booting from 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 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Bootloader_Disk_Selection.md b/docs/documentation/QA/Testcase_Bootloader_Disk_Selection.md index 2fcd572..bbde0fa 100644 --- a/docs/documentation/QA/Testcase_Bootloader_Disk_Selection.md +++ b/docs/documentation/QA/Testcase_Bootloader_Disk_Selection.md @@ -16,10 +16,10 @@ rc: ## 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' %} +{% include 'qa_data_loss_warning.md' %} ## Setup -{% include 'testing/qa_setup_boot_to_media.md' %} +{% 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: ![Full disk summary and bootloader...](/assets/images/bootloader.png){ loading=lazy } @@ -31,4 +31,4 @@ This test case verifies that the user is able to select an alternative disk on w 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' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Custom_Boot_Methods_Boot_Iso.md b/docs/documentation/QA/Testcase_Custom_Boot_Methods_Boot_Iso.md index b5fb18d..cb87435 100644 --- a/docs/documentation/QA/Testcase_Custom_Boot_Methods_Boot_Iso.md +++ b/docs/documentation/QA/Testcase_Custom_Boot_Methods_Boot_Iso.md @@ -29,4 +29,4 @@ This is to verify that the Anaconda installer starts correctly when booting from 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 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Debranding.md b/docs/documentation/QA/Testcase_Debranding.md index a94f5e8..264c434 100644 --- a/docs/documentation/QA/Testcase_Debranding.md +++ b/docs/documentation/QA/Testcase_Debranding.md @@ -197,4 +197,4 @@ This testcase will verify that all packages available on released media that Roc $ umount /media ``` -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Disk_Layouts.md b/docs/documentation/QA/Testcase_Disk_Layouts.md index f8a4133..0d20c8a 100644 --- a/docs/documentation/QA/Testcase_Disk_Layouts.md +++ b/docs/documentation/QA/Testcase_Disk_Layouts.md @@ -16,10 +16,10 @@ rc: ## 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' %} +{% include 'qa_data_loss_warning.md' %} ## Setup -{% include 'testing/qa_setup_boot_to_media.md' %} +{% include 'qa_setup_boot_to_media.md' %} ## How to test 1. Select the Installation Destination spoke. @@ -58,4 +58,4 @@ The following openQA test suites satisfy this release criteria: - `install_multi` - `install_multi_empty` -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Firmware_RAID.md b/docs/documentation/QA/Testcase_Firmware_RAID.md index 2d00bc7..c96c4c3 100644 --- a/docs/documentation/QA/Testcase_Firmware_RAID.md +++ b/docs/documentation/QA/Testcase_Firmware_RAID.md @@ -27,4 +27,4 @@ The installer must be able to detect and install to firmware RAID devices. Note 1. This is what you should see/verify. 2. You should also see/verify this. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Installation_Interfaces.md b/docs/documentation/QA/Testcase_Installation_Interfaces.md index 8627e98..40b0054 100644 --- a/docs/documentation/QA/Testcase_Installation_Interfaces.md +++ b/docs/documentation/QA/Testcase_Installation_Interfaces.md @@ -16,10 +16,10 @@ rc: ## Description This test case verifies that the installer can complete an installation using all Anaconda spokes. -{% include 'testing/qa_data_loss_warning.md' %} +{% include 'qa_data_loss_warning.md' %} ## Setup -{% include 'testing/qa_setup_boot_to_media.md' %} +{% include 'qa_setup_boot_to_media.md' %} ## How to test @@ -52,4 +52,4 @@ TODO - set security policy --> -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Installer_Help.md b/docs/documentation/QA/Testcase_Installer_Help.md index 0892e0d..9cfe903 100644 --- a/docs/documentation/QA/Testcase_Installer_Help.md +++ b/docs/documentation/QA/Testcase_Installer_Help.md @@ -17,7 +17,7 @@ rc: 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' %} +{% 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. @@ -43,4 +43,4 @@ The following openQA test suites satisfy this release criteria: - `anaconda_help` -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Installer_Translations.md b/docs/documentation/QA/Testcase_Installer_Translations.md index 8f70da2..a052160 100644 --- a/docs/documentation/QA/Testcase_Installer_Translations.md +++ b/docs/documentation/QA/Testcase_Installer_Translations.md @@ -17,7 +17,7 @@ rc: The installer must correctly display all complete translations that are available for use. ## Setup -{% include 'testing/qa_setup_boot_to_media.md' %} +{% include 'qa_setup_boot_to_media.md' %} ## How to test 1. From the Language Selection spoke, select a language. @@ -34,4 +34,4 @@ The following openQA test suites satisfy this release criteria: - `install_cyrillic_language` - `install_european_language` -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Kickstart_Installation.md b/docs/documentation/QA/Testcase_Kickstart_Installation.md index 1ff0eef..1763890 100644 --- a/docs/documentation/QA/Testcase_Kickstart_Installation.md +++ b/docs/documentation/QA/Testcase_Kickstart_Installation.md @@ -16,12 +16,12 @@ rc: ## Description This test case verifies that installations via both local and remote Kickstart configuration files are successful. -{% include 'testing/qa_data_loss_warning.md' %} +{% 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 'testing/qa_setup_boot_to_media.md' %} +{% 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`. @@ -38,4 +38,4 @@ The following openQA test suites satisfy this release criteria: - `server_realmd_join_kickstart` -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Media_File_Conflicts.md b/docs/documentation/QA/Testcase_Media_File_Conflicts.md index 8164285..aec8878 100644 --- a/docs/documentation/QA/Testcase_Media_File_Conflicts.md +++ b/docs/documentation/QA/Testcase_Media_File_Conflicts.md @@ -172,4 +172,4 @@ This testcase will verify that the offline repository included on release blocki $ sudo umount /media ``` -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Media_Repoclosure.md b/docs/documentation/QA/Testcase_Media_Repoclosure.md index 8f7224b..d2be195 100644 --- a/docs/documentation/QA/Testcase_Media_Repoclosure.md +++ b/docs/documentation/QA/Testcase_Media_Repoclosure.md @@ -83,4 +83,4 @@ This testcase will verify that the offline repository included on release blocki Error: Repoclosure ended with unresolved dependencies. ``` -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Media_USB_dd.md b/docs/documentation/QA/Testcase_Media_USB_dd.md index 37df444..aede135 100644 --- a/docs/documentation/QA/Testcase_Media_USB_dd.md +++ b/docs/documentation/QA/Testcase_Media_USB_dd.md @@ -58,4 +58,4 @@ This verifies that Rocky Linux ISO image can be written to USB media using `dd` **[OPTIONALLY]**
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 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Minimal_Installation.md b/docs/documentation/QA/Testcase_Minimal_Installation.md index 7ad1599..705dee6 100644 --- a/docs/documentation/QA/Testcase_Minimal_Installation.md +++ b/docs/documentation/QA/Testcase_Minimal_Installation.md @@ -16,10 +16,10 @@ rc: ## 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' %} +{% include 'qa_data_loss_warning.md' %} ## Setup -{% include 'testing/qa_setup_boot_to_media.md' %} +{% 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. @@ -34,4 +34,4 @@ The following openQA test suites satisfy this release criteria: - `install_minimal` -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Network_Attached_Storage.md b/docs/documentation/QA/Testcase_Network_Attached_Storage.md index a23d1fc..268c4e2 100644 --- a/docs/documentation/QA/Testcase_Network_Attached_Storage.md +++ b/docs/documentation/QA/Testcase_Network_Attached_Storage.md @@ -34,4 +34,4 @@ then unmounted sudo umount /mnt 1. This is what you should see/verify. 2. You should also see/verify this. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Packages_Installer_Sources.md b/docs/documentation/QA/Testcase_Packages_Installer_Sources.md index bc0ac35..35c3f5e 100644 --- a/docs/documentation/QA/Testcase_Packages_Installer_Sources.md +++ b/docs/documentation/QA/Testcase_Packages_Installer_Sources.md @@ -25,10 +25,10 @@ The following package sets are only available from remote sources and require a - graphical-server - virtualization-host -{% include 'testing/qa_data_loss_warning.md' %} +{% include 'qa_data_loss_warning.md' %} ## Setup -{% include 'testing/qa_setup_boot_to_media.md' %} +{% 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. @@ -50,4 +50,4 @@ The following openQA test suites satisfy this release criteria, provided they pa - `install_packageset_graphical-server` - `install_packageset_virtualization-host` -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Packages_No_Insights.md b/docs/documentation/QA/Testcase_Packages_No_Insights.md index a59fe93..f4f115d 100644 --- a/docs/documentation/QA/Testcase_Packages_No_Insights.md +++ b/docs/documentation/QA/Testcase_Packages_No_Insights.md @@ -93,4 +93,4 @@ This test will verify that `insights-client` package is not declared be installe $ sudo umount /media ``` -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Packages_No_RHSM.md b/docs/documentation/QA/Testcase_Packages_No_RHSM.md index 3d66e1c..b3dc123 100644 --- a/docs/documentation/QA/Testcase_Packages_No_RHSM.md +++ b/docs/documentation/QA/Testcase_Packages_No_RHSM.md @@ -60,4 +60,4 @@ This test will verify that packages that are availble from upstream do not have TBD -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Post_Application_Functionality.md b/docs/documentation/QA/Testcase_Post_Application_Functionality.md index efc6af4..d327272 100644 --- a/docs/documentation/QA/Testcase_Post_Application_Functionality.md +++ b/docs/documentation/QA/Testcase_Post_Application_Functionality.md @@ -52,4 +52,4 @@ Obtain access to a suitable system with either a Workstation or a Graphical Serv Make sure that the individual applications behave as they should. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Post_Artwork_and_Assets.md b/docs/documentation/QA/Testcase_Post_Artwork_and_Assets.md index 5edb3a9..3e3ac65 100644 --- a/docs/documentation/QA/Testcase_Post_Artwork_and_Assets.md +++ b/docs/documentation/QA/Testcase_Post_Artwork_and_Assets.md @@ -41,4 +41,4 @@ There are several brand artworks and assets throughout the whole OS, this testca The tests during the process could be successfully finished. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Post_GNOME_UI_Functionality.md b/docs/documentation/QA/Testcase_Post_GNOME_UI_Functionality.md index 14f560b..13ac9a4 100644 --- a/docs/documentation/QA/Testcase_Post_GNOME_UI_Functionality.md +++ b/docs/documentation/QA/Testcase_Post_GNOME_UI_Functionality.md @@ -42,4 +42,4 @@ Obtain access to a suitable system with either a Workstation or a Graphical Serv 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 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Post_Identity_Management.md b/docs/documentation/QA/Testcase_Post_Identity_Management.md index 31fe9cd..eebe5a2 100644 --- a/docs/documentation/QA/Testcase_Post_Identity_Management.md +++ b/docs/documentation/QA/Testcase_Post_Identity_Management.md @@ -65,4 +65,4 @@ Setting up a IdM system (FreeIPA) and using it's functionality leverages not als After installation all services should be available and work correctly. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Post_Keyboard_Layout.md b/docs/documentation/QA/Testcase_Post_Keyboard_Layout.md index d57e72e..52906ac 100644 --- a/docs/documentation/QA/Testcase_Post_Keyboard_Layout.md +++ b/docs/documentation/QA/Testcase_Post_Keyboard_Layout.md @@ -57,4 +57,4 @@ Check that the chosen keyboard layout works correctly on text mode. The tests during the process could be successfully finished. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Post_Module_Streams.md b/docs/documentation/QA/Testcase_Post_Module_Streams.md index 97401c8..3cbe1e2 100644 --- a/docs/documentation/QA/Testcase_Post_Module_Streams.md +++ b/docs/documentation/QA/Testcase_Post_Module_Streams.md @@ -46,4 +46,4 @@ This could be automated with i.e. Ansible to do all the `install -> rollback -> 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 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Post_Multimonitor_Setup.md b/docs/documentation/QA/Testcase_Post_Multimonitor_Setup.md index 053ab48..28cbd04 100644 --- a/docs/documentation/QA/Testcase_Post_Multimonitor_Setup.md +++ b/docs/documentation/QA/Testcase_Post_Multimonitor_Setup.md @@ -33,4 +33,4 @@ You will need either a machine which can be reinstalled with multiple screens, o There shouldn't be any graphical glitches, or scaling issues through the install and the usage. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Post_Package_installs.md b/docs/documentation/QA/Testcase_Post_Package_installs.md index adedd55..fafe2bc 100644 --- a/docs/documentation/QA/Testcase_Post_Package_installs.md +++ b/docs/documentation/QA/Testcase_Post_Package_installs.md @@ -52,4 +52,4 @@ Obtain access to a suitable system where any of the tested packages can be insta Installs work without any issues. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Post_SELinux_Errors_Desktop.md b/docs/documentation/QA/Testcase_Post_SELinux_Errors_Desktop.md index 7eb01fe..8497c3e 100644 --- a/docs/documentation/QA/Testcase_Post_SELinux_Errors_Desktop.md +++ b/docs/documentation/QA/Testcase_Post_SELinux_Errors_Desktop.md @@ -35,4 +35,4 @@ Obtain access to a suitable system with either a Workstation or a Graphical Serv 1. Open the SETroubleshoot Application and invoke the error summarization. 2. There must not be shown any errors / denials -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Post_SELinux_Errors_Server.md b/docs/documentation/QA/Testcase_Post_SELinux_Errors_Server.md index 72fde65..d2a7c87 100644 --- a/docs/documentation/QA/Testcase_Post_SELinux_Errors_Server.md +++ b/docs/documentation/QA/Testcase_Post_SELinux_Errors_Server.md @@ -37,4 +37,4 @@ It might also be beneficial to run this test with other than the core installati 2. Run `sealert -a /var/log/audit/audit.log` 3. There must not be shown any errors / denials -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Post_System_Services.md b/docs/documentation/QA/Testcase_Post_System_Services.md index ddd3734..366ba87 100644 --- a/docs/documentation/QA/Testcase_Post_System_Services.md +++ b/docs/documentation/QA/Testcase_Post_System_Services.md @@ -38,4 +38,4 @@ systemctl status The tests during the process could be successfully finished. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Repo_Compare.md b/docs/documentation/QA/Testcase_Repo_Compare.md index 4136a8c..10751f1 100644 --- a/docs/documentation/QA/Testcase_Repo_Compare.md +++ b/docs/documentation/QA/Testcase_Repo_Compare.md @@ -25,4 +25,4 @@ This test case will verify that repositories and the packages within them match 1. Rocky Linux repositories should match, as closely as possible, upstream repositories. 2. The content of Rocky Linux packages should match, as closely as possible, upstream repositories. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Storage_Volume_Resize.md b/docs/documentation/QA/Testcase_Storage_Volume_Resize.md index 2ba9478..3548f26 100644 --- a/docs/documentation/QA/Testcase_Storage_Volume_Resize.md +++ b/docs/documentation/QA/Testcase_Storage_Volume_Resize.md @@ -16,10 +16,10 @@ rc: ## 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' %} +{% include 'qa_data_loss_warning.md' %} ## Setup -{% include 'testing/qa_setup_boot_to_media.md' %} +{% include 'qa_setup_boot_to_media.md' %} ## How to test @@ -51,4 +51,4 @@ The following openQA test suites satisfy this release criteria: - `install_delete_pata` - `install_resize_lvm` -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Template.md b/docs/documentation/QA/Testcase_Template.md index 4e65294..20dbb50 100644 --- a/docs/documentation/QA/Testcase_Template.md +++ b/docs/documentation/QA/Testcase_Template.md @@ -25,4 +25,4 @@ Add a short description here for this Testcase. 1. This is what you should see/verify. 2. You should also see/verify this. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_Update_Image.md b/docs/documentation/QA/Testcase_Update_Image.md index c30812a..c3af4f7 100644 --- a/docs/documentation/QA/Testcase_Update_Image.md +++ b/docs/documentation/QA/Testcase_Update_Image.md @@ -15,10 +15,10 @@ rc: 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' %} +{% include 'qa_data_loss_warning.md' %} ## Setup -{% include 'testing/qa_setup_boot_to_media.md' %} +{% include 'qa_setup_boot_to_media.md' %} 1. Hit the Tab key to edit the boot command ## How to test @@ -48,4 +48,4 @@ The following openQA test suites satisfy this release criteria: [Fedora QA:Testcase Anaconda updates.img via URL](https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_URL)
[Fedora QA:Testcase Anaconda updates.img via local media](https://fedoraproject.org/wiki/QA:Testcase_Anaconda_updates.img_via_local_media)
-{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/QA/Testcase_VNC_Graphics_Mode.md b/docs/documentation/QA/Testcase_VNC_Graphics_Mode.md index 8dab859..89ede76 100644 --- a/docs/documentation/QA/Testcase_VNC_Graphics_Mode.md +++ b/docs/documentation/QA/Testcase_VNC_Graphics_Mode.md @@ -14,7 +14,7 @@ rc: ## Description This test case will verify that release-blocking installers function as intended using the VNC installation method on supported systems and classes of hardware. -{% include 'testing/qa_testcase_supported_systems.md' %} +{% include 'qa_testcase_supported_systems.md' %} ## Setup 1. Obtain access to supported system and hardware class to be installed. @@ -43,4 +43,4 @@ This test case will verify that release-blocking installers function as intended 4. After reboot system boots into graphical environment. 5. After login user is able to operate the graphical environment. -{% include 'testing/qa_testcase_bottom.md' %} +{% include 'qa_testcase_bottom.md' %} diff --git a/docs/documentation/dev_guides/wiki_development_boxes.md b/docs/documentation/dev_guides/wiki_development_boxes.md index a2b4aeb..66b23fc 100644 --- a/docs/documentation/dev_guides/wiki_development_boxes.md +++ b/docs/documentation/dev_guides/wiki_development_boxes.md @@ -50,4 +50,4 @@ From the root of this repository on a machine with Docker installed, run When the container finishes starting up, you can access the documentation in your web browser at [http://localhost:8000](http://localhost:8000). -{% include 'testing/rc_content_bottom.md' %} +{% include 'rc_content_bottom.md' %} diff --git a/docs/guidelines/release_criteria/r8/8_release_criteria.md b/docs/guidelines/release_criteria/r8/8_release_criteria.md index 04aa5a9..59b4000 100644 --- a/docs/guidelines/release_criteria/r8/8_release_criteria.md +++ b/docs/guidelines/release_criteria/r8/8_release_criteria.md @@ -274,4 +274,4 @@ It should be possible to setup a IdM server (FreeIPA), use it's functionality an - Test cases - [QA:Testcase Identity Management](Testcase_Post_Identity_Management.md) -{% include 'testing/rc_content_bottom.md' %} +{% include 'rc_content_bottom.md' %} diff --git a/docs/guidelines/release_criteria/r9/9_release_criteria.md b/docs/guidelines/release_criteria/r9/9_release_criteria.md index f49ff3c..519d83e 100644 --- a/docs/guidelines/release_criteria/r9/9_release_criteria.md +++ b/docs/guidelines/release_criteria/r9/9_release_criteria.md @@ -274,4 +274,4 @@ It should be possible to setup a IdM server (FreeIPA), use it's functionality an - Test cases - [QA:Testcase Identity Management](Testcase_Post_Identity_Management.md) -{% include 'testing/rc_content_bottom.md' %} +{% include 'rc_content_bottom.md' %}