Testing: Add Testcase_VNC_Graphics_Mode (#37)

* add Testcase_VNC_Graphics_Mode
* suggest but do not require specific VNC clients
* complete description and add examples
* update QA testcases index

QA/Testcase_Basic_Graphics_Mode.md

@@ -1,7 +1,7 @@
 ---
 title: QA:Testcase Basic Graphics Mode
 author: Trevor Cooper
-revision_date: 2022-05-18
+revision_date: 2022-06-23
 rc:
   prod: Rocky Linux
   ver: 8
@@ -9,10 +9,10 @@ rc:
 ---
 
 !!! error "REFERENCED RELEASE CRITERIA IS OVERLY GENERAL AND UNTESTABLE"
-    The associated release criteria, [Release_Criteria#basic-graphics-mode-behaviors](9_release_criteria.md#basic-graphics-mode-behaviors), for this test case is overly general and **must** be modified to specific enough to be testable.
+    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](9_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.
+    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.

QA/Testcase_Custom_Boot_Methods_Boot_Iso.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 'testing/qa_testcase_bottom.md' %}

QA/Testcase_VNC_Graphics_Mode.md

@@ -0,0 +1,46 @@
+---
+title: QA:Testcase VNC Graphics Mode
+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 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' %}
+
+## 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)
+3. Obtain access to remote system with a VNC client installed to use for VNC connection.
+
+
+!!! info "Suggested VNC Clients"
+    Both [`tigervnc`](https://tigervnc.org) and [`vinagre`](https://wiki.gnome.org/Apps/Vinagre) are VNC clients provided in Rocky Linux but any VNC client may be used.
+
+## How to test
+1. Boot the system from the prepared optical, USB media or virtual device attachment.
+    - Examples: [QA:Testcase Custom Boot Methods Boot ISO](Testcase_Custom_Boot_Methods_Boot_Iso.md)
+2. Interrupt the kernel boot and specify the appropriate VNC installation option on the boot command line.
+3. Proceed with installation on the test system.<br>**Depending on installer choices this MAY destroy all the data on the test system.**
+4. Depending on the choice or `direct` or `connect` mode connect inbound to the system under test or wait for it to connect to your listening VNC client.
+
+!!! 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. Connection to (with direct mode) or from (in connect mode) to the Anaconda installer using VNC 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 'testing/qa_testcase_bottom.md' %}

qa_test_cases.md

@@ -1,6 +1,6 @@
 ---
 title: QA:Test Cases
-revision_date: 2022-05-19
+revision_date: 2022-06-23
 rc:
   prod: Rocky Linux
 ---
@@ -13,10 +13,11 @@ This page lists all test cases in work and who is working on them...
 | --------------------------------------------------- | ------------------------------------------------------------------------ | ----------------------- | --------------------------------------- |
 | Release-blocking images must boot<br>[{{ rc.prod }} 8](8_release_criteria.md#release-blocking-images-must-boot) [{{ rc.prod }} 9](9_release_criteria.md#release-blocking-images-must-boot) | [QA:Testcase Boot Methods Boot ISO](Testcase_Boot_Methods_Boot_Iso.md) | @tcooper | template exists, openQA covered (ref) |
 | Release-blocking images must boot<br>[{{ rc.prod }} 8](8_release_criteria.md#release-blocking-images-must-boot) [{{ rc.prod }} 9](9_release_criteria.md#release-blocking-images-must-boot) | [QA:Testcase Boot Methods DVD](Testcase_Boot_Methods_Dvd.md) | @tcooper | template exists, openQA covered (ref) |
-| Basic Graphics Mode behaviors<br>[{{ rc.prod }} 8](8_release_criteria.md#basic-graphics-mode-behaviors) [{{ rc.prod }} 9](9_release_criteria.md#basic-graphics-mode-behaviors) | [QA:Testcase Basic Graphics Mode](Testcase_Basic_Graphics_Mode.md) | @tcooper | manual and/or new openQA TestCase |
+| Basic Graphics Mode behaviors<br>[{{ rc.prod }} 8](8_release_criteria.md#basic-graphics-mode-behaviors) | [QA:Testcase Basic Graphics Mode](Testcase_Basic_Graphics_Mode.md) | @tcooper | openQA TestCase |
+| VNC Graphics Mode behaviors<br>[{{ rc.prod }} 9](9_release_criteria.md#vnc-graphics-mode-behaviors) | [QA:Testcase VNC Graphics Mode](Testcase_VNC_Graphics_Mode.md) | @tcooper | openQA TestCase |
 | No Broken Packages<br>[{{ rc.prod }} 8](8_release_criteria.md#no-broken-packages) [{{ rc.prod }} 9](9_release_criteria.md#no-broken-packages) | [QA:Testcase Media Repoclosure](Testcase_Media_Repoclosure.md)<br>[QA:Testcase Media File Conflicts](Testcase_Media_File_Conflicts.md) | @tcooper | manual using scripts or automated in CI |
 | Repositories Must Match Upstream<br>[{{ rc.prod }} 8](8_release_criteria.md#repositories-must-match-upstream) [{{ rc.prod }} 9 ](9_release_criteria.md#repositories-must-match-upstream) | [QA:Testcase repocompare](Testcase_Repo_Compare.md) | @tcooper | manual using Skip's repocompare |
-| Debranding<br>[{{ rc.prod }} 8](8_release_criteria.md#debranding) [{{ rc.prod }} 9](9_release_criteria.md#debranding) | [QA:Testcase Debranding Analysis](Testcase_Debranding.md) | @tcooper | process TBD |
+| Debranding<br>[{{ rc.prod }} 8](8_release_criteria.md#debranding) [{{ rc.prod }} 9](9_release_criteria.md#debranding) | [QA:Testcase Debranding Analysis](Testcase_Debranding.md) | @tcooper | manual using scripts or automated in CI |
 
 
 ## Installer Requirements

release_criteria/r9/9_release_criteria.md

@@ -49,11 +49,11 @@ Release-blocking installer images must boot when written to optical media or USB
         - [QA:Testcase Boot Methods DVD](Testcase_Boot_Methods_Dvd.md)
         - [QA:Testcase Media USB dd](Testcase_Media_USB_dd.md)
 
-#### Basic Graphics Mode behaviors
+#### VNC Graphics Mode behaviors
-The generic video driver option (“basic graphics mode”) on all release-blocking installers must function as intended. This means launching the installer or desktop and attempting to use a generic driver. There must be no bugs that prevent the installer from being reached in this configuration on all systems and classes of hardware supported by the enterprise linux kernel.
+The VNC installation option on all release-blocking installers must function as intended. This means launching the installer or desktop and connecting with VNC to complete the installation. There must be no bugs that prevent the installer from being reached in this configuration on all systems and classes of hardware supported by the enterprise linux kernel.
 ??? tldr "References"
     - Test cases:
-        - [QA:Testcase Basic Graphics Mode](Testcase_Basic_Graphics_Mode.md)
+        - [QA:Testcase VNC Graphics Mode](Testcase_VNC_Graphics_Mode.md)
 
 #### No Broken Packages
 Critical errors, such as undeclared conflicts, unresolved dependencies, or modules relying on packages from another stream will be considered an automatic blocker. There are potential exceptions to this (eg, freeradius cannot be installed on an older perl stream, this is a known issue upstream).