From Fedora Project Wiki

No edit summary
(obsolete this)
 
(3 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{admon/important|This test case is obsolete|This has been merged into [[QA:Testcase Anaconda User Interface VNC]].}}
{{QA/Test Case
{{QA/Test Case
|description=This test verifies the vnc option '''vncpassword''' work as expected. See [[Anaconda/Options]] for more information.
|description=This test verifies the vnc option '''vncpassword''' work as expected. See [[Anaconda/Options]] for more information.
|setup=
* Requires two systems able to communicate over the network, one to test the installation and a second to initiate the VNC client session
* Install a VNC client application.  The package {{package|tigervnc}} or {{package|vinagre}} can be used. This test will use {{command||vinagre}} <pre>yum install /usr/bin/vinagre</pre>
|actions=
|actions=
<ol>
<ol>
<li>Boot the installer with the command-line option(added as a kernel option in boot selection screen):
<li>Boot the installer with the following command-line options (added as a kernel option in boot selection screen).  Replace <code>&lt;password&gt;</code> with a password of your choosing.
<pre>
<pre>
vnc vncpassword=<password>
vnc vncpassword=<password>
Line 20: Line 25:
09:59:02 Starting graphical installation.
09:59:02 Starting graphical installation.
</pre></li>
</pre></li>
<li>Connect with VNC client (vncviewer, vinagre) to the specified address and enter the password set up in previous step , you should see the graphical installation.
<li>Using a VNC client, connect to the specified address.  When prompted, enter the <code>password</code> provided in the previous step.
<pre>
<pre>
vinagre 192.168.1.17:1
vinagre 192.168.1.17:1
</pre></li>
</pre></li>
<li>Proceed and complete installation with VNC client.</li>
<li> Using the VNC client session, complete the installation as desired
</ol>
</ol>
|results=
|results=
# Anaconda starts Xvnc properly  
# Anaconda starts Xvnc properly  
# User can connect with VNC client
# User can connect with VNC client using a valid password
# VNC works normally during installation (mouse, keyboard)
# VNC works normally during installation (mouse, keyboard)
# Anaconda completes successfully
# Anaconda completes successfully
# Reboot successfully into installed system
# The installed system boots into runlevel 3 (no graphical session)
}}
}}


[[Category:User Interface]]
[[Category:Obsolete Test Cases]]

Latest revision as of 15:42, 12 November 2012

This test case is obsolete
This has been merged into QA:Testcase Anaconda User Interface VNC.


Description

This test verifies the vnc option vncpassword work as expected. See Anaconda/Options for more information.

Setup

  • Requires two systems able to communicate over the network, one to test the installation and a second to initiate the VNC client session
  • Install a VNC client application. The package tigervnc or vinagre can be used. This test will use
    yum install /usr/bin/vinagre

How to test

  1. Boot the installer with the following command-line options (added as a kernel option in boot selection screen). Replace <password> with a password of your choosing.
    vnc vncpassword=<password>
    
  2. Watch the text messages printed out, you should see something like this:
    Running anaconda 15.31, the Fedora system installer - please wait.             
    09:59:01 Starting VNC...
    09:59:02 The VNC server is now running.
    09:59:02 
    
    You chose to execute vnc with a password.
    
    09:59:02 Please manually connect your vnc client to 192.168.1.17:1 to begin the install.
    09:59:02 Starting graphical installation.
    
  3. Using a VNC client, connect to the specified address. When prompted, enter the password provided in the previous step.
    vinagre 192.168.1.17:1
    
  4. Using the VNC client session, complete the installation as desired

Expected Results

  1. Anaconda starts Xvnc properly
  2. User can connect with VNC client using a valid password
  3. VNC works normally during installation (mouse, keyboard)
  4. Anaconda completes successfully
  5. The installed system boots into runlevel 3 (no graphical session)