Filer_Windows - Windows Filer - Test Plan

Preparation

Host platform

The tests described here for the Windows Filer appliance are designed to run on an AppLogic 2.4.x+ grid. The automated tests are to be run as a maintainer on the grid controller.

3rd-party tools

None

Test Summary

The unit test for the Windows Filer tests the various modes of operation for the appliance.

Boundary Tests

Verify all mandatory properties must be set and unsupported modes or file system types cannot be specified.

format Tests

Verify the Windows Filer can format a volume to all supported file systems.

fscopy Tests

Verify the Windows Filer can perform a filesystem-level copy of one volume to another.

fsck Tests

Verify the Windows Filer can check the file system on a volume and report if there are errors.

fsrepair Tests

Verify the Windows Filer can check and repair the file system on a volume.

manual Tests

Verify the Windows Filer can provide user-level access to a volume. This test also tests the eXtplorer Web GUI and verifies ssh access to the filer.

Verify a filesystem-level copy of a Windows boot volume also boots.

Running the Tests

To run the tests on the controller of an AppLogic grid, copy and uncompress the tests archive file (filer_windows_test.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). Finally, run the tests:

./runall.sh

When necessary, the script will prompt for manual intervention. All tests are automated except for testing the Web GUI. Any errors are logged to filer_windows-tst.log.

Design

Structure

Test Details

Boundary Tests

• Provision the application without setting any properties and verify the build fails. A message should be displayed for each mandatory property.
• Provision the application and specify an unsupported mode. Verify the build fails.
• Provision the application and specify an unsupported fs_type. Verify the build fails.
• Provision the application and do not specify a dst volume. Verify the build fails.

format Tests

• For each file system type, provision the application with mode set to format. Verify the Windows Filer correctly formats the volume. Execute the tests for volumes of the following sizes: 50 MB, 200 MB, 1 GB, 20 GB, 100 GB.
• While the volumes are being formatted, get status through the default interface and verify there is no GUI or ssh access to the filer. Verify progress is not reported.

fscopy Tests

• For each file system type, provision the application with mode set to fscopy. Verify the Windows Filer correctly copies the contents from src to dst. Execute the tests for volumes of the following sizes: 50 MB, 200 MB, 1 GB, 20 GB, 100 GB.
• While the volumes are being copied, get status through the default interface and verify there is no GUI or ssh access to the filer. Verify progress is reported.
• Provision the application without specifying a src volume. Verify the fscopy fails.
• Manually perform a filesystem-level copy of a Windows boot volume and verify that the copy boots without error.

fsck Tests

• For each file system type, provision the application with mode set to fsck. Verify the Windows Filer correctly determines a volume without any file system errors is OK and a volume with file system errors needs repair. Execute the tests for volumes with and without errors and of the following sizes: 50 MB, 200 MB, 1 GB, 20 GB, 100 GB.
• While the volumes are being checked, get status through the default interface and verify there is no GUI or ssh access to the filer.

fsrepair Tests

• For each file system type, provision the application with mode set to fsrepair. Verify the Windows Filer correctly determines a volume without any file system errors is OK and a volume with file system errors needs repair and actually fixes the errors. Execute the tests for volumes with and without errors and of the following sizes: 50 MB, 200 MB, 1 GB, 20 GB, 100 GB.
• While the volumes are being checked, get status through the default interface and verify there is no GUI or ssh access to the filer.

manual Tests

• For each file system type, provision the application with mode set to manual. Verify the Windows Filer provides GUI access to the volume and ssh access to the filer. Execute the tests for volumes of the following sizes: 50 MB, 200 MB, 1 GB, 20 GB, 100 GB.
• From the GUI:
  • Verify files can be accessed and directories can be traversed
  • Verify files and directories can be copied to and from the volume, if in read-write mode
  • Verify permissions and ownership on files and directories can be modified, if in read-write mode
• From SSH:
  • Verify files can be accessed and directories can be traversed
  • Verify files and directories can be modified, if in read-write mode
• Verify getting status through the default interface fails.
• Disable the external interface on the filer (ip_addr=0.0.0.0, invalid ip_addr, invalid netmask, or invalid gateway) and verify there is no external network access.
• Manually perform a filesystem-level copy of a Windows boot volume and verify that the copy boots without error.

-- StephenQ - 23 Jun 2008