MDDK MCICORE Test Case Descriptions
===================================

The following document lists each of the Test Cases in the mcicore.exe
Test Application.

Each Test Case will be identified by Test Case Number, a one-line
description (which appears in the Test Shell's list box in the
Select Tests Dialog), and a short outline of the code executed in the
test case.  

Each test case refers to a driver, element and a path to elements.
Each test case is invoked using the mciSendString command.
The driver and element are entered in the "Parameters!" dialog box.
The compound tests use the element extension also specified in the 
"Parameters!" dialog box along with the input path specified in the
input and output paths dialog box (see test shell description for 
more details).

Case 1: Simple: Open/Close Device
        Opens and closes the driver specified.

Case 2: Simple: Open/Close Shareable Device
        Opens and closes the driver specified as shareble.

Case 3: Simple: Open/Close Full Device Test
        Stress the open and close commands of the specified
        driver while the driver is in either open or closed
        state.

Case 4: Simple: Open/Close Shareable Full Device Test
        Stress the open with the shareable flag and close 
        commands of the specified driver while the driver is 
        in either open or closed state.

Case 5: Simple: Open/Play/Close Device Test  
        Opens, plays and closes the specified driver.

Case 6: Simple: Open/Play/Close Shareable Device Test
        Opens shareable, plays and closes the specified driver.

Case 7: Simple: Required Commands Device Test
        Invokes the commands that are labelled in the MCI documentation
        as required commands with the specified driver.

Case 8: Simple: Play/Mode Test
        Invokes the play command and status mode command with the 
        specified driver during different states of the driver.

Case 9: Simple: Parsing Device Test
        Invokes different play commands with different parameters
        with the specified driver.

Case 10: Simple: Parsing Device Commands Test
        Invokes all the commands for the specified driver that the 
        driver is required to recognize.

Case 11: Simple: Info Device Parameter Test 
        Invokes the info command with all possible parameters that the
        specified driver should recognize.

Case 12: Simple: Parsing Capability Device Test
        Invokes the capability command with all possible parameters 
        that the specified driver should recognize.

Case 13: Simple: Status Device Parameter Test 
        Invokes the status command with all possible parameters 
        that the specified driver should recognize.

Case 14: Simple: Sysinfo 'All' Device Test
        Invokes the sysinfo command with the keyword "all" as the 
        driver name and all possible parameters for the command.

Case 15: Simple: Stress Device with Aliases Test
        Stresses the specified element with open commands with 
        different aliases that stress the use of the alias keyword.

Case 16: Compound: Open/Close Device
        Opens and closes the element specified.

Case 17: Compound: Open/Close Shareable Device
        Opens and closes the element specified as shareble.

Case 18: Compound: Open/Close Full Device Test
        Stress the open and close commands of the specified
        element while the element is in either open or closed
        state.

Case 19: Compound: Open/Close Shareable Full Device Test
        Stress the open with the shareable flag and close 
        commands of the specified element while the element is 
        in either open or closed state.

Case 20: Compound: Open/Play/Close Device Test  
        Opens, plays and closes the specified element.

Case 21: Compound: Open/Play/Close Shareable Device Test
        Opens shareable, plays and closes the specified element.

Case 22: Compound: Required Commands Device Test
        Invokes the commands that are labelled in the MCI documentation
        as required commands with the specified element.

Case 23: Compound: Play/Mode Test
        Invokes the play command and status mode command with the 
        specified element during different states of the element.

Case 24: Compound: Parsing Device Test
        Invokes different play commands with different parameters
        with the specified element.

Case 25: Compound: Parsing Device Commands Test
        Invokes all the commands for the specified element that the 
        element is required to recognize.

Case 26: Compound: Info Device Parameter Test 
        Invokes the info command with all possible parameters that the
        specified element should recognize.

Case 27: Compound: Parsing Capability Device Test
        Invokes the capability command with all possible parameters 
        that the specified element should recognize.

Case 28: Compound: Status Device Parameter Test 
        Invokes the status command with all possible parameters 
        that the specified element should recognize.

Case 29: Compound: Sysinfo 'All' Device Test
        Invokes the sysinfo command with the keyword "all" as the 
        element and all possible parameters for the command.

Case 30: Compound: Stress Element with Aliases Test
        Stresses the specified element with open commands with 
        different aliases that stress the use of the alias keyword.

      

