Share via


Print Driver Stress Test

This automated test stresses the driver in several ways. You do not have to examine the output from this test.

Note  

You must run this test separately from the other printer tests.

 

Test details

Associated requirements

Device.Imaging.Printer.Base.applicationVerifier

See the device hardware requirements.

Platforms

Windows 7 (x64) Windows 7 (x86) Windows 8 (x64) Windows 8 (x86) Windows Server 2012 (x64) Windows Server 2008 R2 (x64) Windows 8.1 x64 Windows 8.1 x86 Windows Server 2012 R2

Expected run time

~150 minutes

Categories

Reliability

Type

Automated

 

Running the test

Before you run the test, complete the test setup as described in the test requirements: Printer Testing Prerequisites.

Note  

This test does not require a printer to be physically attached to the test computer. You can run this test by using a null port. However, you must run this test in the Appverifier environment. You must enable the NT system debugger (NTSD).

 

Troubleshooting

For troubleshooting information, see Troubleshooting Device.Imaging Testing.

This test fails if any of the following problems occur:

  • The test does not produce output.

  • The debugger breaks in.

  • The test produces incorrect output.

  • The log file indicates a failure.

The following are the log files for this test:

  • Printdrvstress.xml

  • PrintDrvStress_DeviceLogger.xml

More information

This test can generate lots of output. You can ignore and discard this output.

This test exercises several driver code paths on multiple threads. This test exercises both the rendering and configuration portion of the driver. This exercise creates a stress environment for the printer drivers. The tool often reveals bugs.

Typically, this test prints to a NULL port printer to avoid large quantities of physical output.

To run this test manually, run the following command at a command prompt:

PrintDrvStress.exe /printer="<printername>” /timetorun=120

This test uses the "Add NullPortMonitor and switch port" and "Restore port and delete NullPortMonitor" test jobs in the Windows HCK library to automatically run PrintDrvStress by using a null port and then to restore the printer port.

 

 

Send comments about this topic to Microsoft