QA:Testcase Anaconda User Interface serial console

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(Updated guidance for using systemd)
(add 'serial' option, it's needed for anaconda)
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
 
|description=
 
|description=
This test is intended to ensure that the console= parameter is honored and the post-installed systems is configured properly for a non tty0 console.  While the examples mention the use of ''console=ttyS0'', it it acceptable to use any device other than the default ''tty0''.
+
This test is intended to ensure that the ''console=X serial'' parameters are honored and the post-installed systems is configured properly for a non tty0 console.  While the examples mention the use of ''console=ttyS0'', it it acceptable to use any device other than the default ''tty0''.
 
{{Admon/note|Serial Cable?| This test case may require using a DB-9 serial cable to connect to the system under test.  Additionally, you may be required to update the BIOS to enable the serial port.}}
 
{{Admon/note|Serial Cable?| This test case may require using a DB-9 serial cable to connect to the system under test.  Additionally, you may be required to update the BIOS to enable the serial port.}}
 
{{Admon/tip|Go Virtual|Since the focus of this test is not to validate the physical DB-9 serial cable connection, or to ensure the cables are seated properly, it is entirely acceptable (and ''encouraged'') to use [[Virtualization]].  For example, creating any KVM/QEMU virtual guest with the correct ''console{{=}}ttyS0 serial'' will setup a serial console for use with this test.}}
 
{{Admon/tip|Go Virtual|Since the focus of this test is not to validate the physical DB-9 serial cable connection, or to ensure the cables are seated properly, it is entirely acceptable (and ''encouraged'') to use [[Virtualization]].  For example, creating any KVM/QEMU virtual guest with the correct ''console{{=}}ttyS0 serial'' will setup a serial console for use with this test.}}
 
|actions=
 
|actions=
 
# Using a DB-9 serial cable, connect to your test system on the first port (typically S0) and start a serial port monitoring application (ttywatch, cermit, or minicom)
 
# Using a DB-9 serial cable, connect to your test system on the first port (typically S0) and start a serial port monitoring application (ttywatch, cermit, or minicom)
# Boot installation program passing the console=ttyS0 command line parameter
+
# Boot installation program passing the ''console=ttyS0 serial'' command line parameters
 
# Complete installation and boot into installed system
 
# Complete installation and boot into installed system
 
|results=
 
|results=

Revision as of 09:08, 3 August 2011

Description

This test is intended to ensure that the console=X serial parameters are honored and the post-installed systems is configured properly for a non tty0 console. While the examples mention the use of console=ttyS0, it it acceptable to use any device other than the default tty0.

Note.png
Serial Cable?
This test case may require using a DB-9 serial cable to connect to the system under test. Additionally, you may be required to update the BIOS to enable the serial port.
Idea.png
Go Virtual
Since the focus of this test is not to validate the physical DB-9 serial cable connection, or to ensure the cables are seated properly, it is entirely acceptable (and encouraged) to use Virtualization. For example, creating any KVM/QEMU virtual guest with the correct console=ttyS0 serial will setup a serial console for use with this test.


How to test

  1. Using a DB-9 serial cable, connect to your test system on the first port (typically S0) and start a serial port monitoring application (ttywatch, cermit, or minicom)
  2. Boot installation program passing the console=ttyS0 serial command line parameters
  3. Complete installation and boot into installed system

Expected Results

  1. The installation displays properly and responds to user input over the serial line
  2. Confirm that a login console is presented over the serial device. When using Package-x-generic-16.pngsystemd (Fedora 15 and newer), you may confirm that the serial device is configured for login by examining the output of systemctl status serial-getty@ttyS0.service. For example:
    	  Loaded: loaded (/lib/systemd/system/serial-getty@.service)
    	  Active: active (running) since Tue, 01 Mar 2011 12:46:54 -0500; 4min 29s ago
    	Main PID: 736 (login)
    	  CGroup: name=systemd:/system/serial-getty@.service/ttyS0
    

    When using Package-x-generic-16.pngupstart (from Fedora 9 to Fedora 14), you may confirm that the serial device is configured for login by examining the output of initctl status serial DEV=ttyS0. For example:

    serial (ttyS0) start/running, process 1210
  3. The file /etc/securetty contains a line matching the requested console and the user is able to login to the system using the serial login prompt