Credential Manager Test (Compact 2013)
3/26/2014
The Credential Manager Test verifies that an installed Credential Type Provider supports basic functionality. The test lists the registry settings for all credential types and Credential Providers associated with each type, verifies that required functions are exported in the library, and makes calls to those functions.
This test does not require user interaction. There is no timeout value set in the test itself.
Test Prerequisites
Your device must meet the following requirements before you run this test.
This test has no specific hardware requirements.
The following table shows the software requirements for the Credential Manager Test.
Requirements |
Description |
|---|---|
Tux.exe |
Test harness, required for executing the test |
Kato.dll |
Logging engine, required for logging test data |
credtest.dll |
Test library |
Subtests
The table below lists the subtests included in this test.
SubTest ID |
Description |
|---|---|
1 |
Primitive types. Lists all credential providers for primitive types that are installed in the system. This test case prints out registry information; it does not check the existence or integrity of the libraries. |
2 |
Virtual types. Lists all credential providers for virtual types that are installed in the system. This test case basically prints out registry information; it does not check the existence or integrity of the libraries. |
Setting Up the Test
This test has no additional requirements beyond the standard test environment setup.
Running the Test
COMMAND LINE PARAMETERS:
The Credential Manager Test executes the tux -o -d credtest command line on default execution, which runs all test cases. To run a specific test case, use tux -o -d credtest -x test_case, where test_case is the number of the test case you wish to run.
There are no other command line parameters for this test.
Verifying the Test
When the test completes running, verify that "PASS" appears in the test log for all subtests.
Troubleshooting the Test
Verify that credential manager is included in the image.
Determine the point of failure and record the exact error message. Check that the proper steps were followed and that all prerequisites were met. If the source code is available, examine the point of failure in code to see if any additional information can be gathered about the failure domain.