Modifying the DirectDraw Test
The DirectDraw Test runs the tux –o –d DdrawTK command-line entry on default execution. 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. The following table shows the modifications you can make to the test.
To modify the DirectDraw Test
| To | Add this command-line parameter |
|---|---|
| Run test cases 1200 through 1360 interactively.
If you specify this option, the test prompts you to verify that each image for these test cases displays correctly. |
|
| Pause the test while displaying each image for test cases 1200 through 1360.
If you specify this option, the test pauses momentarily to allow you to view the image. The test does not allow you to provide data indicating whether the image is correctly displayed. If the test encounters an unrecognized pixel format, the test can continue, but the colors displayed may not match the expected colors. |
|
| Automate the test.
If you specify this option, the test verifies internally that each image displays correctly. |
|
The following table shows the test cases for the DirectDraw Test.
| Test case | Description |
|---|---|
| 100: Get Caps | Retrieves the capabilities of the hardware abstraction layer (HAL), verifies that the operation is successful, and then displays all capabilities retrieved. This test case fails if it cannot retrieve the capabilities of the HAL. |
| 101: Enumerate Display Modes | Enumerates the DirectDraw display modes, verifies that the enumeration completes, and then displays the results of the enumeration. |
| 200: Blt (Windowed Mode) | Executes blits to and from various surfaces. The test case verifies that the actual destination matches the expected destination for each blit. This test case fails if any blits are unsuccessful. |
| 210: ColorKey Blt (Windowed Mode) | Executes a variety of color key blits to and from assorted surfaces. The test case verifies that the actual destination matches the expected destination for each test. This test case fails if any color key blits are unsuccessful. |
| 220: Color Filling Blts (Windowed Mode) | Executes a variety of color fill blits to assorted surfaces. The test case verifies that the surface is filled with the specified color. This test case fails if any color fill blits are unsuccessful. |
| 300: Blt (Exclusive Mode) | Executes a variety of blits to and from assorted surfaces. The test case verifies that the actual destination matches the expected destination for test. This test case fails if any blits are unsuccessful. |
| 310: ColorKey Blt (Exclusive Mode) | Executes a variety of color key blits to and from assorted surfaces. The test case verifies that the actual destination matches the expected destination for each test. This test case fails if any color key blits are unsuccessful. |
| 320: Color Filling Blts (Exclusive Mode) | Executes a variety of color fill blits to assorted surfaces. The test case verifies that the surface is filled with the specified color. This test case fails if any color fill blits are unsuccessful. |
| 330: Flip (Exclusive Mode) | Executes a variety of blits to a flipping chain and verifies that the flips are successful and that all surfaces display correctly. This test case fails if any flips or surface verifications fail. |
| 400: CreateVideoPort (Video Port Container Test) | Enumerates the available video ports and connections for the video ports. This test case then verifies that each enumerated connection can be created. |
| 410: EnumVideoPorts (Video Port Container Test) | Enumerates the available video ports and then enumerates the video ports based on specific capabilities. |
| 420: GetVideoPortConnectInfo (Video Port Container Test) | Verifies that the GetVideoPortConnectInfo function appropriately handles a variety of input conditions. |
| 430: QueryVideoPortStatus (Video Port Container Test) | Verifies that the QueryVideoPortStatus function appropriately handles each video port. |
| 500: GetBandwidthInfo (Video Port Test) | Verifies that the GetBandwidthInfo function returns consistent information about each type of video port available. |
| 502: GetSetColorControls (Video Port Test) | Verifies that the GetColorControls and SetColorControls functions set and return consistent color controls if the color control feature is supported. |
| 504: GetInputOutputFormats (Video Port Test) | Verifies that the GetInputFormats and GetOutputFormats functions return consistent information under a variety of calling conditions. |
| 506: GetFieldPolarity (Video Port Test) | Verifies that the GetFieldPolarity function returns consistent information about the field polarity of a video port. |
| 508: GetVideoLine (Video Port Test) | Verifies that the GetVideoLine function returns consistent information. |
| 510: GetVideoSignalStatus (Video Port Test) | Verifies that the GetVideoSignalStatus function returns consistent information. |
| 512: SetTargetSurface (Video Port Test) | Verifies that the SetTargetSurface function appropriately handles improper input. |
| 514: StartVideo (Video Port Test) | Verifies that calls to the StartVideo function succeed with a variety of flags set. |
| 516: StopVideo (Video Port Test) | Verifies that a call to the StopVideo function succeeds. |
| 518: UpdateVideo (Video Port Test) | Verifies that calls to the UpdateVideo function succeed with a variety of flags set. |
| 520: WaitForSync (Video Port Test) | Verifies that the WaitForSync function behaves consistently with each possible flag. |
| 1200: Blt (Interactive Windowed Mode) | Executes blits that include color fills and scaling. You must manually verify that each blit is successful. |
| 1240: Overlay Blt (Interactive Windowed Mode) | Executes blits to an overlay surface. The test cannot verify that the contents of the overlay surface display correctly, so you should manually verify that the output is correct. If the test succeeds, an overlay appears in the middle of the screen with a blue and yellow checkerboard pattern. This test may run as many as three times with the same output, testing RGB, YUYV, and VYUY pixel formats on the overlay surface. |
| 1250: ColorKeyOverlay Blt (Interactive Windowed Mode) | Executes color key blits to an overlay surface. The test cannot verify that the contents of the overlay surface display correctly, so you should manually verify that the output is correct. If the test succeeds, a blue checkerboard pattern appears in a variety of locations across the display of the target device. If the driver enables stretching, the test also stretches the checkerboard pattern. This test may run as many as three times with the same output, testing RGB, YUYV, and VYUY pixel formats on the overlay surface. |
| 1260: ColorFill Overlay Blt (Interactive Windowed Mode) | Executes color fill blits to an overlay surface. The test cannot verify that the contents of the overlay surface display correctly, so you should manually verify that the output is correct. This test case cycles through red, green and blue on the primary overlay surface. This test may run as many as three times with the same output, testing RGB, YUYV, and VYUY pixel formats on the overlay surface. |
| 1300: Blt (Interactive Exclusive Mode) | Executes blits that you must verify when prompted. The test does not contain an automated mechanism for verifying scaling. |
| 1340: Overlay Blt (Interactive Exclusive Mode) | Executes blits to an overlay surface. The test cannot verify that the contents of the overlay surface display correctly, so you should manually verify that the output is correct. If the test succeeds, an overlay is located in the middle of the screen on the target device with blue and yellow horizontal lines. The primary surface behind the overlay surface should fill the entire display. This test may run as many as three times with the same output, testing RGB, YUYV, and VYUY pixel formats on the overlay surface. |
| 1350: ColorKeyOverlay Blt (Interactive Exclusive Mode) | Executes color key blits to an overlay surface. The test cannot verify that the contents of the overlay surface display correctly, so you should manually verify that the output is correct. If the test succeeds, blue horizontal bars appear across the display of the target device. The primary surface behind the overlay surface should fill the entire display. This test may run as many as three times with the same output, testing RGB, YUYV, and VYUY pixel formats on the overlay surface. |
| 1360: ColorFill Overlay Blt (Interactive Exclusive Mode) | Executes color fill blits to an overlay surface. The test cannot verify that the contents of the overlay surface display correctly, so you should manually verify that the output is correct. This test case cycles through red, green and blue on the primary surface and the overlay surface. The color fills on the primary surface should fill the entire display. This test may run as many as three times with the same output, testing RGB, YUYV, and VYUY pixel formats on the overlay surface. |
For information about problems that you may encounter while running the DirectDraw Test, see Troubleshooting: DirectDraw Test Failed.
Note 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
–ccommand-line option. This option forces Tux to pass the specified string into the test library.
See Also
Last updated on Friday, October 08, 2004
© 1992-2003 Microsoft Corporation. All rights reserved.