WIN03- Windows Server - Test Plan

Preparation

Host platform

The tests described here for the WIN03 appliance are designed to run on an AppLogic 2.4 grid.

3rd-party tools

Tests Summary

• Verify that the appliance can be started/stopped with varying memory and CPU resources
• Verify that the appliance's terminals are operational
• Verify that the appliance starts and stops correctly over 100 times
• Verify that counters are operational.

Running the Tests

Copy and uncompress the test harness archive win03-tst-app.tar.bz2 on the impex volume of the grid controller. Import the test application.

Copy and uncompress the test script archive win03-tst.tar.bz2 on the impex volume of the grid controller. Update the setenv.sh file to setup the proper test environment (i.e., IP address, etc.). Finally, run the tests:

./runall.sh

All tests are automated except for testing the Windows counters. Any errors are logged to win-server-tst.log.

This is a diagram of the test harness:

Design

Structure

• a Windows 2003 server win03
• an input gateway in used to verify the in terminal
• a net gateway net used to verify the net terminal
• a monitoring appliance mon used to verify the mon terminal and counters
• a web appliance srv used to verify the out terminal

Test Details

Verify that the appliance can be started/stopped with varying memory and CPU resources

• Start the test application with sched=crunch --cap_cpu. Execute the terminal tests to verify the appliance is operational.
• Re-start the test application with default resources. Execute the terminal tests to verify the appliance is operational.
• Re-start the WIN03 appliance with mem=1024 cpu=2. Execute the terminal tests to verify the appliance is operational.

Verify that the appliance's terminals are all operational

• default interface: SSH to the appliance from 3t shell and execute various commands - ls, ipconfig, etc.
• in: SSH to the appliance through the IN gateway IP and verify that the resulting shell is the Cygwin bash on WIN03.
• net: SSH to the appliance and verify that ping returns success for both an IP and domain name.
• out: SSH to the appliance and verify wget http://out returns success.
• mon: SSH to the appliance and verify wget http://mon returns success.

Verify that the appliance starts and stops correctly 100 times

• Re-start the WIN03 appliance 100 times. Each time, execute the terminal tests to verify the appliance is operational.

Verify that counters are operational

Open a monitoring view of the test application and manually verify that all counters are present. Create a bash script which generates CPU load and disk IO. Verify counter values change appropriately. The following counters are functional for Windows appliances:

• CPU Summary
  • CPU Idle
  • CPU Irq
  • CPU System
  • CPU Total
  • CPU User
• Interface / Terminals
  • Recvd bytes
  • Recvd packets
  • Sent bytes
  • Sent packets
• Memory
  • Cached
  • Free
• Schedular
  • Context Switches
  • Interrupts
  • Pages IN
  • Pages OUT
  • Process startups
  • Processes blocked
  • Processes running
• Volume
  • Bytes read
  • Bytes written
  • Disk Reads
  • Disk Writes
  • Free Space
  • Time Spent in Reads
  • Time Spent in Writes

-- BeckyH - 11 Aug 2008