Share via


Driver Scenario

This automated test verifies that the display adapter can meet the minimum Microsoft® Direct3D® requirements. For the full list of minimum requirements, refer to the latest Windows Logo Program (WLP) documentation.

The test composes a Direct3D scene that includes all of the relevant elements from the WLP minimum requirements, such as Gouraud shading, basic alpha blending, bi-linear filtering, specific texture formats, and so on. The test then renders the scene with the display adapter and with the reference rasterizer.

The test does a pixel comparison of the rendered images and determines if the test passed or failed based on that comparison (allowing the standard 15 percent difference).

This topic applies to the following test jobs:

  • Driver Scenario

  • Driver Scenario (WoW64)

Test details

Associated requirements

Device.Graphics.AdapterRender.MinimumDirectXLevel

See the device hardware requirements.

Platforms

Windows 7 (x64) Windows 7 (x86) Windows RT (ARM-based) Windows 8 (x64) Windows 8 (x86) Windows Server 2012 (x64) Windows Server 2008 R2 (x64) Windows RT 8.1 Windows 8.1 x64 Windows 8.1 x86 Windows Server 2012 R2

Expected run time

~5 minutes

Categories

Certification Functional

Type

Automated

 

Running the test

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

In addition, this test requires the following software and hardware:

  • Microsoft DirectX® version 7.0 or later

  • Display adapter with Direct3D capabilities

Troubleshooting

For troubleshooting information, see Troubleshooting Device.Graphics Testing.

More information

Command syntax

Command option Description

Scenario -M:1 -dx9 -whql -logclean

Runs the Driver Scenario test job.

Scenario -M:1 -whql -logclean

Runs the Driver Scenario (WoW64) test job.

 

Note  

For command line help for this test binary, type /?.

 

File list

File Location

Configdisplay.exe

<[testbinroot]>\nttest\windowstest\tools\

D3d10ref.dll

<[testbinroot]>\nttest\graphics\d3d\support\

D3d11ref.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dcompiler_test.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dref.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support

D3dref8.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dref9.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dx10_test.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dx11_TEST.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dx8d.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

D3dx9_TEST.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\support\

Fpstate.dll

<[testbinroot]>\nttest\windowstest\graphics\d3d\utility\

Modechange.exe

<[testbinroot]>\nttest\windowstest\graphics\d3d\utility\

Scenario.exe

<[testbinroot]>\nttest\

TDRWatch.exe

<[testbinroot]>\nttest\windowstest\graphics\

Vbswap.x

<[testbinroot]>\nttest\windowstest\graphics\d3d\conf\

 

 

 

Send comments about this topic to Microsoft