Direct3D Mobile Interface Test (Windows CE 5.0)
The Direct3D Mobile Interface Test verifies Direct3D Mobile functionality by inspecting the return values of functions and other results conveyed by function parameters. This test does not assess rendered output. For information about assessing rendered output, see Direct3D Mobile Driver Comparison Test.
The Direct3D Mobile Interface Test includes one or more callers for each interface in the Microsoft® Direct3D® Mobile API. To verify that a driver is functionally correct, run this test on a run-time image built from a Debug configuration that includes the Direct3D Mobile middleware and on a run-time image built from a Release configuration that includes the Direct3D Mobile middleware. The former scenario provides extensive validation of function calls, while the latter scenario causes function calls that are not valid to generate device driver interface (DDI) calls that the driver must handle gracefully.
The following tasks are examples of tasks that the Direct3D Mobile Interface Test performs:
- Verifies consistency between the D3DMDEVICEFORMAT support as reported in the D3DM_GETADAPTERINFO_DATA structure and actual support as evidenced by surface creation attempts
- Verifies that the content of the D3DMCAPS structure for the driver is consistent with the functionality of the driver
- Verifies that the driver gracefully handles function calls that are not valid
- Verifies that the driver handles valid function calls
Some function calls in this test cause the Direct3D Mobile middleware to invoke entry points to the DDI of the Direct3D Mobile driver. These function calls force the driver to provide a functionally correct implementation of each entry point. The test causes the Direct3D Mobile middleware to invoke the D3DM_DRAWPRIMITIVE_PTR entry point in the driver with a variety of data in the command buffer, including every value in the D3DM_OPERATION enumeration. The driver reports DDI entry points by using the D3DM_INITIALIZE_DATA structure.
The following table shows the hardware requirements for the Direct3D Mobile Interface 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 Interface 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_Interface.dll | Dynamic-link library for the test. |
For the Direct3D Mobile Interface Test to run, in your OS design, set the SYSGEN_D3DM variable. You must also include a Direct3D Mobile driver in your OS design.
Note When you run the Direct3D Mobile Interface 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.6 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 Interface Test | Test Cases for the Direct3D Mobile Interface Test | Direct3D Mobile | Direct3D Mobile Display Drivers
Send Feedback on this topic to the authors