WGF11 Draw

This automated test verifies that the behavior of draw calls of the graphics drivers/hardware meets the DX11 specification.

This topic applies to the following test jobs:

• WGF11 Draw

• WGF11 Draw (WoW64)

Test details

Additional documentation

Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):

• Device.Graphics additional documentation

Running the test

Before you run the test, complete the test setup as described in the test requirements: Graphic Adapter or Chipset Testing Prerequisites.

Troubleshooting

For generic troubleshooting of HLK test failures, see Troubleshooting Windows HLK Test Failures.

For troubleshooting information, see Troubleshooting Device.Graphics Testing.

Test cases return one of the following results:

• Pass

• Fail

• Blocked

• Skipped

The log file will contain specific details about the test cases that are failed, blocked, or skipped. A test case will return Skipped if it is invalid according to the current hardware configuration (some features are optional and may not be supported by some hardware) and the command line options (some test cases are only valid for certain feature levels). A test case will return Blocked if the failure is caused by reasons other than the tested feature. To review test details, review the test log from the Windows HLK Manager.

More information

In the Draw test group:

• Draw functions are cycled, including Draw(), DrawIndexed(), DrawInstanced() and DrawIndexedInstanced().

• The vertex buffer size, vertex buffer offset, index buffer size, and index buffer offset cycle through different values.

• The number of elements in the vertex buffer and the input classification cycle through different values.

• The number of vertices to draw and the start vertex location cycle through different values.

• Other parameters that are specific to different draw functions, including index count, start index location, instance count, start instance location, and base vertex location, also cycle through different values.

• Test results are read back from the stream output buffer and verified against expected values.

• Pipeline statistics, including VSInvocations, IAPrimitives, and IAVertices are verified.

In the DrawIndirect test group:

• Draw indirect functions are cycled, including DrawInstancedIndirect() and DrawIndexedInstancedIndirect().

• The methods to fill in the argument buffer include UpdateSubresource, StreamOutput buffer, RenderTarget buffer, and CopyStructureCount.

• The aligned byte offset for the argument buffer cycles through different values.

• Test results are read back from the stream output buffer and verified against expected values.

• Pipeline statistics, including VSInvocations, IAPrimitives, and IAVertices are verified.

Command syntax

File list

Parameters