alangm/wiki
1
0
Fork 0
forked from testing/wiki
Code Pull Requests Activity
483766fd50
wiki/docs/documentation/QA/Testcase_VNC_Graphics_Mode.md

2.3 KiB
Raw Blame History

title author revision_date rc
QA:Testcase VNC Graphics Mode Trevor Cooper 2022-06-23
prod ver level
Rocky Linux 9 Final

!!! info "Associated release criterion" This test case is associated with the Release_Criteria#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 '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.
  3. Obtain access to remote system with a VNC client installed to use for VNC connection.

!!! info "Suggested VNC Clients" Both tigervnc and 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.
  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.
    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 'qa_testcase_bottom.md' %}