Touch BVT Test (Compact 7)
3/12/2014
This test verifies if the touch driver is loaded and registered correctly in the registry.
Test Prerequisites
Your device must meet the following requirements before you run this test.
The following tables show the hardware requirements for the Touch BVT Test.
| Requirement | Description |
|---|---|
Touch panel |
A device which supports the touch driver for testing. |
The following table shows the software requirements for the Touch BVT Test.
| Requirements | Description |
|---|---|
Tux.exe |
Test harness, required to execute the test. |
Kato.dll |
Logging engine, required for logging test data. |
touchbvt.dll |
Library that contains the test cases. |
Touch driver |
An installed touch driver. |
NOTE:
The TouchBVT.DLL test suite verifies the touch driver information is found in the following registry key: "HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch".
If a different registry key was used in the BSP the test cases in the suite may fail.
Subtests
The table below lists the subtests included in this test.
| SubTest ID | Description |
|---|---|
1 |
Touch Verify Registry Test. Verifies whether entries required for the touch driver architecture exist in the registry exist. |
2 |
TouchVerifyDriversLoadedTest. Verifies whether the touch driver, proxy touch driver, and calibration driver (if you specify them in the registry) are loaded. |
3 |
Touch Driver Active Test. Verifies whether the Device Manager registered the touch driver correctly in the registry. |
Setting Up the Test
This test has no additional setup requirements beyond the standard test environment setup.
Running the Test
Command-line Parameters for the Touch BVT Test
The following table shows the command-line parameters for the Touch BVT Test.
| Command-line parameter | Description |
|---|---|
-v |
Driver name of the DLL. If no driver name is specified, then touch.dll will be taken as the driver name. |
Verifying the Test
When the test completes running, it will report a PASS or FAIL result for all subtests in the test log.
Troubleshooting the Test
*If the test ID 1 fails then it indicates that there are missing registry keys or registry key values, or both.
*If the test ID 2 fails then it indicates one or more DLLs are not loaded.
NOTE:
The TouchBVT.DLL test suite verifies the touch driver information is found in the following registry key: "HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Touch".
If a different registry key was used in the BSP the test cases in the suite may fail.
For additional platform specific issues, consult the CTK articles on the TechNet wiki.