Share via

Running the PCMCIA Controller Driver Test

  • Article

The PCMCIA Controller Driver Test executes the tux -o -d ddlx -c"Pcmcetsts" command line on default execution. The PCMCIA Controller Driver Test includes 117 unique test cases. Each test case runs in five different scenarios, meaning that 585 test cases run on default execution. The following table shows the scenarios for each test case.

Scenario Description
1 Single-function PC Card in socket 0.

You can substitute a multiple-function PC Card for the single-function PC Card in this scenario.
2 Single-function PC Card in socket 1.

You can substitute a multiple-function PC Card for the single-function PC Card in this scenario.
3 Multiple-function PC Card in socket 0.

The multiple-function PC Card must expose at least two functions, or the test fails.
4 Multiple-function PC Card in socket 1.

The multiple-function PC Card must expose at least two functions, or the test fails.
5 PC Card in socket 0 and PC Card in socket 1 at the same time.

In the command line for the PCMCIA Controller Driver Test, you must specify the number of the scenario immediately to the left of the number for the test case.

To run the PCMCIA Controller Driver Test

  • If you plug a single-function PC Card into socket 0, run the test with the tux -o -d ddlx -c"Pcmcetsts" -x11001-16105 command line.

    - or -

    If you plug a single-function PC Card into socket 1, run the test with the tux -o -d ddlx -c"Pcmcetsts" -x21001-26105 command line.

    - or -

    If you plug a multiple-function PC Card into socket 0, run the test with the tux -o -d ddlx -c"Pcmcetsts" -x31001-36105 command line.

    - or -

    If you plug a multiple-function PC Card into socket 1, run the test with the tux -o -d ddlx -c"Pcmcetsts" -x41001-46105 command line.

    - or -

    If you plug PC Cards into both socket 0 and socket 1, run the test with the tux -o -d ddlx -c"Pcmcetsts" -x51001-56105 command line to run tests on both cards at the same time.

If you modify the command line for the test to specify socket 0 or socket 1, the test does not run until you plug a card into the slot that you specified. For information about how to edit the command line for a test, see Editing the Command Line for a Test.

If you plug in a PC Card prior to launching the test, when you launch the test a dialog box prompts you to remove the card. After you remove the card, the test updates the registry, and then prompts you with a second dialog box to plug in the PC Card. After you plug in the requested card, the test runs.

If you do not plug in a PC Card prior to launching the test, when you launch the test the test updates the registry and then prompts you with a dialog box to plug in a PC Card. After you plug in the requested card, the test runs.

Note   For a headless device, a debug message appears in the Microsoft Platform Builder IDE rather than a dialog box on the display of the target device.

The following table shows the test cases for the PCMCIA Controller Driver Test.

Test case Description
<Scenario>1001-<Scenario>1039 Configures the PC Card using the CardRequestConfiguration, CardReleaseConfiguration, and CardAccessConfigurationRegister functions.
<Scenario>2001-<Scenario>2028 Tests window-related functionality. These test cases exercise the CardRequestWindow, CardReleaseWindow, CardMapWindow and CardModifyWindow functions.
<Scenario>3001-<Scenario>3020 Tests interrupt-related functionality. These test cases exercise the CardRequestIRQ and CardReleaseIRQ functions.
<Scenario>4001-<Scenario>4014 Tests mask-related functionality. These test cases exercise the CardGetStatus, CardGetEventMask, CardSetEventMask, CardRequestSocketMask, CardReleaseSocketMask, and CardResetFunction functions.
<Scenario>5001-<Scenario>5012 Verifies that the card supports exclusive access by using the CardRequestExclusive and CardReleaseExclusive functions.
<Scenario>6001-<Scenario>6105 Tests the CardGetFirstTuple, CardGetNextTuple, CardGetParsedTuple, and CardGetTupleData functions.

Remarks

All test cases exercise the CardRegisterClient and CardDeregisterClient functions.

If any test case fails, you can refer to the debug output messages to find out which function calls failed.

See Also

PCMCIA Controller Driver Test

 Last updated on Friday, October 08, 2004

© 1992-2003 Microsoft Corporation. All rights reserved.