Test Cases for the Local Authentication Plugin Test
Other versions of this page are also available for the following:
.gif "A hyphen indicates that the information in this topic is not relevant for this platform, or that the platform does not support the API that is listed.")
.gif "A checkmark indicates that the information in this topic is relevant for this platform, and that any API listed is also supported on this platform.")
8/27/2008
The following table shows the test case descriptions for the Local Authentication Plugin (LAP) Test.
| Test case | Description |
|---|---|
1 |
Lists all LAPs installed in the system. The test prints out registry information. It does not check the existence or integrity of the libraries. |
101 |
Lists all available AEs and their values. The test prints out registry information. The test only prints out String and Numeric Values. |
201 |
Loads the active LAP and calls its InitLAP and DeinitLAP functions. |
301 |
Loads the active LAP, calls InitLAP, CreateEnrollmentDialog, and DeinitLAP. The test will report the return value of the CreateEnrollmentDialog function; however, it does not expect it to return TRUE. |
401 |
Loads the active lap, calls InitLAP, VerifyUser, and DeinitLAP. The test will report the return value of VerifyUser, and expects it to return TRUE; if it returns FALSE, the test will report a failure. This test case uses AE_EVERY_TIME as the AE. |
Note
Depending on the active LAP, the test may require user interaction. There is no timeout value set in the test itself. User interface and hardware requirements depend on the active LAP.