Modifying the Graphics Device Interface Test (Windows CE 5.0)
The GDI Test executes the tux –o –d gdiapi.dll command line on default execution.
The test compares the display output to the output of a GPE–based display driver. If the output of the display driver does not match the output rendered by the GPE–based display driver, the test lists the coordinates and pixel values that do not match.
To view the output of a GPE–based display driver, boot a target device with the flat display driver and then run the test.
You can modify the test by editing the command line. See Editing the Command Line for a Test.
The following table shows the modifications you can make to the test.
To modify the Graphics Device Interface Test
| To | Add this command-line parameter |
|---|---|
| Display information about command-line options for the GDI Test. | |
| Instruct the GDI Test to save a bitmap image for each failure.
The .bmp file can assist you in debugging the problem that caused the unexpected output. |
|
| Specify where to save the bitmap image for a failure. | |
| Instruct the GDI Test to not use driver verification.
By default, the GDI Test uses driver verification. |
|
| Force the GDI Test to perform verification.
If you specify this option, the GDI Test performs verification even if there is little memory available. If the Ddi_test.dll module is not available, test cases fail. |
|
| Instruct the GDI Test to support manual verification.
During manual verification, to step through test cases, press the left SHIFT key. |
|
| Specify the screen to run the GDI Test on.
This option applies only to the Win_Primary surface and only to a Windows CE–based device with multiple screens. If you specify this option and the option does not apply, the GDI Test ignores the option. |
|
| Run the GDI Test spread across multiple screens.
This option applies only to the Win_Primary surface and only to a Windows CE–based device with multiple screens. If you specify this option and the option does not apply, the GDI Test ignores the option. |
|
| Specify the width and height of the surface that the GDI Test uses.
Minimum width is 176. Minimum height is 176. Width and height must each be a multiple of 2. |
|
| Instruct the GDI Test to cycle through all known surfaces.
This cycling can require significant time. The cycling requires significant storage space on the target device because the CETK stores test results in a file on the target device. |
|
| Specify a type of surface to test.
For <surfname>, use one of the following values:
|
|
For information about other command-line parameters for Tux.exe, see Tux Command-Line Parameters.
The following table shows the test cases for the GDI Test.
| Test case | Description |
|---|---|
| 100-104: Clip | Tests the functionality of clipping using different shapes and verifies the functionality of complex clip regions. |
| 200-231: Draw | Calls functions that draw and functions that apply complex effects to drawing.
These test cases perform blitting, line drawing, filling, color table manipulation, bitmap type creation, and device attribute modification. |
| 300-307: Palette | Verifies color matching and color conversion for palettes, and modifies associated palettes. |
| 500-512: Region | Tests region management by calling functions that modify region rectangles. |
| 600-608: Brush and pen | Assesses the functionality of brushes and brush alignments. |
| 700-710: Device attribute | Verifies device attributes and exercises functions that modify device attributes. |
| 800-808: Device context | Creates, retrieves, saves, and restores a device context. |
| 900-905: Device object | Calls functions that retrieve, modify, and delete GDI objects. |
| 1000-1011: Font | Verifies font enumeration, selection, and attributes. |
| 1100-1108: Text | Writes text to various locations on the display.
If the font required by the test is not available, some test cases do not run. |
| 1200-1205: Print | Passes bad parameters to printing functions. |
| 1300-1303: Verify | Assesses the functionality of test verification functions such as CheckScreenHalves and CheckAllWhite. |
| 1400, 1401: Manual | Manually tests font drawing.
You can use these test cases to exercise code paths. To step through these test cases, press the left SHIFT key. |
Remarks
This test library can have one or more optional command-line entries to change the behavior of the test.
To specify one or more optional command-line entries to the test library, you must use the –c command-line option. This option forces Tux to pass the specified string into the test library.
See Also
Graphics Device Interface Test
Send Feedback on this topic to the authors