Share via

Modifying the Graphics Device Interface Test

  • Article

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. For information about how to edit the command line for a test, see Editing the Command Line for a Test.

To modify the Graphics Device Interface Test

  • To instruct the test to send a bitmap (.bmp) image of the display to the release directory when the output does not match the output of the GPE–based display driver, add the -c o option to the command line for the test.

    The .bmp file may assist you in debugging the problem that caused the unexpected output. The -c o option requires a Kernel Independent Transport Layer (KITL) connection between the development workstation and the target device, because the .bmp file is stored in the release directory.

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.
200-219: Draw Draws basic shapes including rectangles, triangles, circles and ellipses. This test case also creates a variety of bitmap images.
600-607: Brush and pen Paints on the display using a variety of sizes and types of pens and brushes.
800-805: Device context Creates, retrieves, saves, and restores a device context.
900-905: Device objects Verifies device objects.
1100-1108, 1200-1203, 1300-1302: Text Writes text to a variety of locations on the display. This test does not run if the font required by the test is not available.

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

 Last updated on Friday, October 08, 2004

© 1992-2003 Microsoft Corporation. All rights reserved.