Share via

Photo Print Test

  • Article

This automated test prints landscape- and portrait-oriented photographs to exercise printer functionality.

Test details

Associated requirements

Device.Imaging.Printer.Base.rendering

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

~2 minutes

Categories

Certification Functional

Type

Automated

 

Running the test

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

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:

  • Photoprinttest.xml

  • Photoprinttest_devicelogger.xml

More information

This test prints five images in both portrait and landscape orientation in addition to the summary page, for a total of 11 pages. You must verify that all the pages are printed, that the picture is correctly rotated, and that the picture fills the page. If the printer prints the bitmap in the same orientation twice, or the bitmap does not stretch to fit the page, the printer has failed the test.

The printer prints the following images:

  • The cover page: Portrait

  • Flower: Portrait and landscape

  • Two children: Portrait and landscape

  • Cow: Portrait and landscape

  • City image: Portrait and landscape

  • Standing rock: Portrait and landscape

PrintSpy is a tool that automatically executes debugger commands when there is an Application Verifier break. The debugger commands depend on the stop code.

Currently, PrintSpy is enabled for the following tests:

  • Document Properties test (ANSI and Unicode)

  • Photo Print test

  • Print Driver Device Capabilities test

  • Print Driver DevMode Corruptor test

  • Print Driver Stress test

  • Printable Area test

  • Printer Port Monitor MIB Verification test

  • PrintTicket test

  • WSDMon Printer Verification test

PrintSpy generates XML logs under %SystemDrive%\Printspy on the client computer. To view the files, open the XML files in the PrintSpy directory on the client computer. After the test completes, the XML logs from %SystemDrive%\PrintSpy are copied to the DTM controller. To view the logs, open DTM Studio, right-click the test, and then select Browse Job Logs.

PrintSpy generates the following two logs:

  • PrintSpy_[TestName].xml

  • PrintSpy_spoolsv_dbg.xml

If the log has only one line that starts with "PrintSpy was unable to continue", no AppVerif breaks were hit.

If the log contains tables, the tables show the stop code or stop codes that PrintSpy hit. The tables also show the commands that PrintSpy executed on the debugger.

Note  

If you are not sure whether the test is running, press Enter in the PrintSpy or debugger window. This causes PrintSpy to execute the last debugger command. If PrintSpy executes a debugger command, the test has stopped. Review the PrintSpy logs and perform additional debugging. If PrintSpy does not execute a debugger command, the test is still running.

 

 

 

Send comments about this topic to Microsoft