Modifying the Partition Driver Test
The Partition Driver Test executes the tux –o –d msparttest command line on default execution.
Warning Prior to running this test, be aware that all information on the storage device is destroyed. The test removes all partition information and writes to and reads from sectors on the storage device without preserving the contents of the sectors. Microsoft recommends that you back up data on all cards and disks that are attached to the tested device before running the test.
You can modify the test by editing the command line. For information about how to edit the command line for a test, see Editing the Command Line for a Test. The following table shows the modifications you can make to the test.
To modify the Partition Driver Test
| To | Add this command-line parameter |
|---|---|
| Specify the name of the custom partition driver.
The default value is Mspart.dll. |
|
The following table shows the test cases for the Partition Driver Test.
| Test case | Description |
|---|---|
| 5001: Partition driver store API | Tests the partition manager storage API set by opening, formatting, and closing stores and by enumerating partitions on a store. This test case fails if any of the basic partition manager operations fail. The test case also fails if the partition information does not persist after a store is closed. |
| 5002: Partition driver API | Tests the partition manager API by creating, deleting, enumerating, and renaming partitions. This test case fails if any of the basic partition manager operations fail. |
| 5101: Create enumerate and delete alternating partitions | Creates partitions of increasing size until the disk is full and then verifies that all partitions are enumerated. The test then repeatedly enumerates and deletes alternating partitions until all partitions are deleted. This test case fails if problems occur in creating partitions. The test case also fails if there is a problem with simultaneously enumerating and deleting partitions. |
| 5102: Create and rename partitions | Creates a partition and then attempts to create a second partition using the same name as the first partition. The test then creates more partitions and attempts to assign names to the partitions that match the names of existing partitions. This test case fails if the partition driver allows multiple partitions to have the same name. The test case also fails if problems occur with creating and renaming a partition. |
| 5103: Read/write and bounds check | Verifies proper input and output on consecutive partitions. The test divides the disk into three partitions and verifies that input and output behaves properly on all partitions. This test case fails if the partition driver does not strictly enforce partition boundaries or if any problems occur with input and output. |
| 5104: Verify disk info IOCTL | Retrieves disk geometry information from the IOCTL_GET_DISK_INFO I/O control code for both the block and partition drivers. Verifies that the information is the same as the information stored in the PD_STOREINFO structure. |
| 5105: Verify PD_STOREINFO | Verifies that the information about free sectors in the PD_STOREINFO structure updates properly when partitions are created and deleted. This test case fails if the value for free sectors does not change by at least the number of sectors in the newly created or deleted partitions. |
| 5106: Test partition boundaries for corruption | Creates three partitions and verifies that it is not possible to perform out-of-bounds input and output operations on each partition. |
Remarks
This test library can have one or more optional command-line entries to change the behavior of the test. To specify one or more optional command-line entries to the test library, you must use the –c command-line option. This option forces Tux to pass the specified string into the test library.
See Also
Last updated on Friday, October 08, 2004
© 1992-2003 Microsoft Corporation. All rights reserved.