Multiple Smart Card Reader Test (Compact 7)
3/12/2014
This test verifies that when more than one smart card reader is attached, all the smart card readers can be used.
Test Prerequisites
Your device must meet the following requirements before you run this test.
The following table shows the hardware requirements for the Multiple Smart Card Reader Test.
| Requirements | Description |
|---|---|
Multiple smart card readers |
The smart card readers that you want to test |
Any of the cards included in the PC/SC Test Cards v.2.0 |
You can obtain a list of these cards from the PC/SC Workgroup Web site:http://www.pcscworkgroup.com/ |
The following table shows the software requirements for the Multiple Smart Card Reader AutoIFD Test.
| Requirements | Description |
|---|---|
Tux.exe |
Test harness, which executes the test |
Kato.dll |
Logging engine, which logs test data |
IFDTestTux.dll |
The Tux DLL that contains the tests |
USBCCID.dll or other smart card reader driver DLL |
The smart card reader driver |
Subtests
The table below lists the subtests included in this test.
| SubTest ID | Description |
|---|---|
3000 |
Multiple Smart Card Reader Test |
Setting Up the Test
This test has no additional requirements, beyond the standard test environment setup.
Running the Test
To run the Multiple Smart Card Reader Test
1.Attach several smart card readers to the system.
2.Insert one of the PC/SC test cards of the IFDTest2 suite into each card reader.
3.At the command-line, type tux -o -d ifdtesttux -x 3000.
4.For each attached smart card reader, the test opens a handle to the reader and runs AutoIFD, the one-card version of the Smart Card Protocol Tests described in the Smart Card Reader Test (IFDTest2) topic. The test then closes the reader handle.
Verifying the Test
When the test completes running, verify that "PASS" appears in the test log for all sub-tests.
Troubleshooting the Test
The following table describes troubleshooting tips for the Multiple Smart Card Reader Test.
| Issue | Solution |
|---|---|
Test fails when using legacy drivers. |
Certain legacy drivers, such as STCUSB.DLL, require that calls to IOCTLs be made from the kernel. If they are not made from the kernel, the test fails.To work around this issue, run Tux using the -n parameter:tux -o -n -d ifdtesttux |
When you are running these test cases on a Windows Embedded CE PC-based development platform (CEPC), if the Smart Card reader is inserted before you turn on the CEPC, USBCCID.dll is not loaded when the CEPC is turned on. |
After you turn on the CEPC, remove the Smart Card reader from the CEPC, and then reinsert it. |
For additional platform specific issues, consult the CTK articles on the TechNet wiki.