1 / 18

Print Driver Testing Tools

Print Driver Testing Tools. Ashwin Needamangala Senior Test Development Lead Documents and Printing Team ashwinn@microsoft.com. Agenda. Driver Quality Challenges Tools for the software development lifecycle Development Phase Tools walk-through Demonstration of development tools

soyala
Download Presentation

Print Driver Testing Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Print Driver Testing Tools Ashwin Needamangala Senior Test Development Lead Documents and Printing Team ashwinn@microsoft.com

  2. Agenda • Driver Quality Challenges • Tools for the software development lifecycle • Development Phase • Tools walk-through • Demonstration of development tools • Testing Phase • Tools walk-through • Demonstration of testing tools • Call to Action

  3. Driver Quality Challenges • Print driver problems hard to find early • No native support for resource tracking in print subsystem • No print-specific tools for extended runtime checks • Numerous distribution vehicles for print-specific developer and test tools • High rate of bug discovery during Windows Logo Kit (WLK) submission runs

  4. Tools for the Software Development Lifecycle (SDL) • Development Phase • Print Verifier • IsXps • PTConform • LooksGood • INFGate • Testing Phase • Print Verifier • Windows Logo Kit (WLK) Tests • XPS Content Library

  5. Development Phase • Print Verifier • Runtime verification tool • Designed to catch violators in the act • Flags errors via debugger breaks • Supports both XPSDrv and GDI drivers • Ships as part of Application Verifier • Verifies print resource usage (leaks, use-after-free, etc.) • Provides runtime PrintSchema conformance verification

  6. Development Phase • IsXps • OPC and XPS conformance validation tool • Easy-to-use command line interface • Detailed error information helps quickly isolate bugs • Ships in the WDK, WLK and SDK • PTConform • PrintSchema conformance validation tool • Easy-to-use command line interface with detailed error information • Ships in the WDK, WLK and SDK • Integrated into Print Verifier for runtime PrintSchema conformance verification

  7. Development Phase • LooksGood • Automated rendering verification tool • Uses Windows Presentation Foundation to render XPS to TIFF • Ships in the WDK and WLK • INFGate • Syntax checker for INF files of print and imaging drivers • Easy-to-use command line interface • Ships in the WDK and WLK

  8. DemoDevelopment Tools

  9. Testing Phase • Print Verifier • Use for detection of incorrect print resource usage (leaked printer handles, use-after-free, thread-unsafe use, etc.) • Turn on runtime PrintSchema conformance validation for easy detection of PrintTicket/PrintCapabilities bugs • Enable fault injection to detect bugs in failure code paths within the driver

  10. Testing Phase • Windows Logo Kit (WLK) Tests • Driver Test Manager (DTM) infrastructure for normal execution of tests • Most tests can be executed without DTM • Copy executable from controller • \\Controller_Name\Tests\<arch>fre\nttest\printscantest\printing • Enable Application Verifier • Spoolsv.exe: Basics + Printing • PrintFilterPipelineSvc.exe: Basics + Printing • Test executable: Basics + Printing • Run Spoolsv.exe and PrintFilterPipelineSvc.exe under debugger • Execute test under debugger

  11. Testing Phase • XPS Content Library • Conformant XPS content from diverse producers • Non-conformant or invalid XPS content (Violate-One) • Corrupted XPS content

  12. DemoHow to run WLK tests without DTM

  13. Distribution Vehicles WDK = Windows Driver Kit WLK = Windows Logo Kit SDK = Software Development Kit

  14. Summary • Numerous easy-to-use tools available • Cover range of software development lifecycle needs • Print Verifier is critically important • Using these tools through your SDL will increase the probability of having a failure-free WLK submission run

  15. Call To Action • Push quality assurance upstream • Get familiar with available tools • Look in WDK, WLK and SDK for these tools • Use tools through all phases of the software development lifecycle • Try out Print Verifier against your XPSDrv filters and GDI minidrivers • Integrate Print Verifier into your development and test environments • Visit the Print Verifier blog

  16. Additional Resources • Print Verifier Blog: http://blogs.msdn.com/PrintVerifier • Newsgroup on www.msdn.com • Microsoft.public.win32.programmer.tools • Tools • Download Application Verifier: http://go.microsoft.com/fwlink/?LinkID=79601 • Application Verifier Documentation:http://msdn2.microsoft.com/en-us/library/aa480483.aspx • Print Devices on the WHDC Web Site: http://www.microsoft.com/whdc/device/print/default.mspx • XPS: http://www.microsoft.com/xps • Email: xpsinfo@microsoft.com and prninfo@microsoft.com

  17. Related Sessions

More Related