[ Legal Information ]

Installation

Suite Description

The Installation suite tests the installation of the distribution, login and user account manipulation.

Execution Frequency

This suite should be used on every system in each beta release during the beta cycle, unless an alternate installation path (RAID, upgrade, dual-boot) was executed.

Execution Dependencies

This suite has no dependencies.

Suite Overview

This suite contains the following cases:

No.   Case Name   Blocking
Case
  Estimated
Execution
  Abandon
After
1   Clean installation   yes   30 min   2 hrs
2   Boot and login   yes   5 min   30 min
3   Users, groups and passwords   no   10 min   1 hr

Revision History

Version   Effective Date   Author/Editor   Summary of Changes
1.1   2001-10-25   Megan Bock   Added shutdown test to Boot and login
Removed folder permissions from Users, groups and passwords
1.0   2001-07-01   Sharon Snider   Original suite



Clean Installation

Do not upgrade or dual-boot in this test. Those installation options are part of other suites. Although this test is suitable for hardware RAID and multiple disk environments, do not use software RAID. That, too, is part of another suite.

Environment Prerequisites

Preferred architecture: any i386
System installed? no
Network configured? n/a
Interface: n/a
Logged in as: n/a

Steps

Results

1
Purpose Install the beta.
Commands Boot off the CD and start a "clean install."
Expected Results  
Comments and Tips You should test both the text and GUI installs at some point during the beta.
 
The remaining "steps" are provided in alphabetical order by KEYWORD. The installer sequence varies from one distribution to the next. Perform each task as indicated in the installer. Refer to product documentation for assistance with the interface.
-
Purpose Add ACCOUNTS and set the root password.
Comments and Tips If the interface supports it, set up multiple user accounts.
 
-
Purpose Choose and configure the BOOTLOADER.
Comments and Tips Some distros offer boot loader options. If this is the case, be sure to test all boot loaders at some point during the beta. Test boot disk creation at least once and verify that the system can be booted from the diskette.
 
-
Purpose Set up the GUI (X-windows).
Comments and Tips  
 
-
Purpose Set up the NETWORK.
Comments and Tips If possible, test both DHCP and static IP at some point during the beta.
 
-
Purpose Select PACKAGES.
Comments and Tips Selecting the "Everything" option in some distros does not always install every package. Use the individual package selection option to verify specific packages you may need.
 
-
Purpose PARTITION and mount the system.
Comments and Tips Some distros require a /boot partition. All will typically require a swap (suggest 256-1000 MB) and a root partition.
 
-
Purpose Set up SECURITY.
Comments and Tips At some point during the beta, install with each security setting.
 
System Attempts Pass Pass
w/Errors
Fail Comments
 
 
         
 
 
         
 
 
         



Boot and login

This test verifies that the boot and login options selected during the installation are the ones used. It also tests user accounts created during the installation.

Environment Prerequisites

Preferred architecture: any i386
System installed? yes
Network configured? yes
Interface: as installed
Logged in as: n/a

Steps

Results

1
Purpose Verify boot loader.
Commands Observe the boot sequence.
Expected Results The bootloader selected in the installation should be the one used by the system.
Comments and Tips  
 
2
Purpose Verify process startup.
Commands Observe the startup sequence. Note any processes that failed unexpectedly.
Expected Results Failed processes are clearly indicated.
Comments and Tips An unplugged network cable may cause the startup to hang for a minute or two when that device is reached.
 
3
Purpose Verify login mode (CLI or GUI).
Commands Note the login prompt.
Expected Results Login mode selected during installation should be presented.
Comments and Tips Sometimes the GUI login takes a moment to start, leaving the CLI prompt temporarily visible.
 
4
Purpose Verify user account.
Commands Log in with a regular user account.
Expected Results Prompt should reflect account name.
Comments and Tips If you chose GUI login, you will need to open a terminal window to view the prompt.
 
5
Purpose Verify root account.
Commands su
Enter the root password.
Expected Results Prompt should reflect root login.
Comments and Tips If you chose the GUI login, you will need to use a terminal window for this step.
 
6
Purpose Verify default desktop.
Commands startx
Expected Results Default desktop should load.
Comments and Tips If you chose GUI login, you will not need to run startx.
 
7
Purpose Verify clean shutdown.
Commands As root, shutdown -h now
Expected Results First processes and then the system should halt.
Comments and Tips Depending on the distro (and your hardware), the computer may power off automatically.
 
System Attempts Pass Pass
w/Errors
Fail Comments
 
 
         
 
 
         
 
 
         



Users, Groups and Passwords

This test verifies that users are created correctly and passwords for those users admit and deny users accordingly.

This case should be run at least once per beta, but need not be executed on every test system.

Environment Prerequisites

Preferred architecture: any i386
System installed? yes
Network configured? n/a
Interface: tester preference
Logged in as: root

Steps

Results

1
Purpose Create a group.
Commands groupadd beta
Expected Results none
Comments and Tips  
 
2
Purpose Create a user and assign the ID to the beta group.
Commands useradd jdoe -g beta
Expected Results none
Comments and Tips  
 
3
Purpose Set the password for jdoe.
Commands passwd jdoe
Expected Results Prompts to enter and confirm the password, followed by a notice of success
Comments and Tips If the password is too short or contains a real word, you will see a BAD PASSWORD message. Disregard the message; the password will still be set as entered.
 
4
Purpose Use the jdoe account.
Commands su jdoe
Expected Results Prompt will change
Comments and Tips Root does not have to enter the password.
 
5
Purpose Check jdoe's group membership.
Commands groups
Expected Results "beta"
Comments and Tips  
 
6
Purpose Check jdoe's password.
Commands 1) Open a second console: In the GUI, press Ctrl + Alt + F3. In the console, press Alt + F3.
2) Log in as yourself.
3) su jdoe
4) Enter an incorrect password.
Expected Results Login should fail.
Comments and Tips  
 
7
Purpose Check jdoe's password.
Commands 1) su jdoe
2) Enter the correct password.
Expected Results The prompt should change to reflect user jdoe.
Comments and Tips Press Alt + F7 to return to the GUI or Alt + F1 to return to the main console window.
 
8
Purpose Delete jdoe.
Commands 1) As root, userdel jdoe
2) su jdoe
Expected Results The su should fail because the user does not exist.
Comments and Tips  
 
System Attempts Pass Pass
w/Errors
Fail Comments
 
 
         
 
 
         
 
 
         

 


 

Legal Information

The information included in this test instruction document is provided AS IS without warranty of any kind. IBM EXPRESSLY DISCLAIMS ANY WARRANTIES, EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. IBM does not warrant any results or performance measurements obtained. Any information concerning IBM products was written for IBM products offered in the U.S.A. IBM may not offer the products, services or features discussed in this document in other countries, and the information is subject to change without notice. The information in this document relating to Linux is provided as a convenience to Linux users, and IBM makes no warranty or representation, express or implied, with respect to the accuracy and completeness of the information, and assumes no responsibility for any errors, which may appear in the document. Any performance or test data contained herein was determined in a controlled test environment. Therefore, the results obtained in other operating environments may vary. No license, express or implied, to any intellectual property is granted by this document. IBM may make improvements and/or changes in product(s) and/or programs described in this publication at any time without notice.

Linux is a trademark of Linus Torvalds.

[ top ]

1