Direct3D Mobile Driver Verification Test (Windows CE 5.0)
The Direct3D Mobile Driver Verification Test assesses the functionality of a Microsoft® Direct3D® Mobile driver.
Unlike the Direct3D Mobile Driver Comparison Test, the Direct3D Mobile Driver Verification Test verifies driver functionality without comparing the output of the driver to the output of the reference driver for Direct3D Mobile. For information about the Direct3D Mobile Driver Comparison Test, see Direct3D Mobile Driver Comparison Test.
Unlike the Direct3D Mobile Interface Test, the Direct3D Mobile Driver Verification Test inspects pixel color values and compares each value to an expected value calculated by the test. For information about the Direct3D Mobile Interface Test, see Direct3D Mobile Interface Test.
The following table shows the hardware requirements for the Direct3D Mobile Driver Verification Test.
| Requirements | Description |
|---|---|
| Hardware dependencies of the driver | Some Direct3D Mobile drivers have specific hardware dependencies. For more information, see the documentation for your driver. |
The following table shows the software requirements for the Direct3D Mobile Driver Verification Test.
| Requirements | Description |
|---|---|
| Tux.exe | Tux test harness, which is required for executing the test. |
| Kato.dll | Kato logging engine, which is required for logging test data. |
| Tooltalk.dll | Application required by Tux.exe and Kato.dll. Handles the transport between the target device and the development workstation. |
| D3DM_DriverVerif.dll | Dynamic-link library for the test. |
| QAD3DMX.dll | Library that supplies functions to compute three-dimensional mathematical operations required by the test. |
For the Direct3D Mobile Driver Verification Test to run, in your OS design, set the SYSGEN_D3DM and SYSGEN_D3DMREF variables. You must also include a Direct3D Mobile driver in your OS design.
Note When you run the Direct3D Mobile Driver Verification Test, the Microsoft® Windows® CE Test Kit (CETK) temporarily copies files to the root directory of the target device. Before running the test, verify that there is at least 0.7 megabytes (MB) of free space in the root directory of the target device. If there is not sufficient space in the root directory of the target device, the test cannot run.
See Also
CETK Tests | Command-Line Parameters for the Direct3D Mobile Driver Verification Test | Test Cases for the Direct3D Mobile Driver Verification Test | Direct3D Mobile | Direct3D Mobile Display Drivers
Send Feedback on this topic to the authors