VDS_WIN03 - VDS based on Windows Server 2003 - Test Plan

Preparation

Host platform

The tests described here for the VDS_Win03x application are designed to run on an AppLogic 2.7+ grid. The tests are to be run as a regular user (i.e, non-maintainer) from a remote server.

3rd-party tools

None

Test Summary

Boundary Tests

• Properties - verify all mandatory properties must be set
• Resources - verify the application is operational with various resource assignments

Root and User Login Tests

• Root access - verify root access to the application
• User access - verify user access to the application

External Network Access Tests

Verify the application can talk to the outside world.

Running the Tests

To run the tests on a remote server, copy and uncompress the tests archive file vds_win03-tst.tar.bz2 to a directory of your choice. Update the setenv.sh file to setup the proper test environment (i.e., list of available IP address, gateway, and other network info). Update setenv.sh and test.openssh to include the public and private key of a regular user on the grid.

Finally, run the tests:

bash runall.sh

When necessary, the script will prompt for manual intervention.

Design

Structure

The test applications are built from the following:

• test utilities and a remote test script, intended to run on a remote server.

Test Details

All tests use the default resource assignment unless otherwise specified.

properties

Provision the application without setting any properties and verify the build fails. A message should be displayed for each mandatory property.

root access

Provision the application and verify root can log into the application with the root password through the appliance's console and by SSHing into the application.

external network access

Before proceeding with tests, make sure your server is not running a proxy server that accepts any value of netmask and gateway otherwise you will get unexpected results when you set invalid netmask and gateway.

• Provision and log into the application. Verify external websites are accessible by both IP address and name by executing wget.
• Verify all dns properties are used by parameterizing one with a valid DNS server and the other two with invalid DNS servers and repeating this test.
• Set the secondary_ip property on the application and verify the application is accessible on this IP address.
• Set an invalid netmask and verify the application is inaccessible.
• Set an invalid gateway and verify the application is inaccessible.

resources

Repeat the above tests with the following resource assignments:

• minimum for all resources, with and without --cap_cpu
• cpu.dflt=1.00, mem.dflt=1G
• cpu.dflt=2.00, mem.dflt=4G
• maximum for all resources (or the max limit of a server)

-- ShubhamGupta - 02 Jul 2008