1 / 41

Print Driver And XPSDrv Testing In Windows Vista

Print Driver And XPSDrv Testing In Windows Vista. Manski Fransazov Test Development Lead Digital Documents Platform and Solutions. Agenda. Topics Test strategy and test areas Test tools and distribution vehicles Justin Slone, Microsoft – XPS Conformance

salena
Download Presentation

Print Driver And XPSDrv Testing In Windows Vista

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 And XPSDrv Testing In Windows Vista Manski FransazovTest Development LeadDigital Documents Platform and Solutions

  2. Agenda • Topics • Test strategy and test areas • Test tools and distribution vehicles • Justin Slone, Microsoft – XPS Conformance • Jim Zuber, QualityLogic – XPS Test Strategies • Should leave today with • Awareness of the test areas • Awareness of the available test tools Assumes basic familiarity with v3 print driver architecture and the new XPSDrv print paths

  3. Test Strategy • Facilitate quality driver development • Facilitate Windows Logo qualification

  4. Test Strategy Implementation • Microsoft to provide in Windows Driver Kit (WDK) • Test tools for format conformance • Baseline XPS content • Test tools targeting print driver (and device) robustness and security • Improve print driver quality by using Application Verifier

  5. Test Areas • GDI-based print drivers and devices • Robustness and security • PrintTicket conformance and manipulation • XPSDrv print drivers and devices • Robustness and security • XPS conformance and manipulation • PrintTicket conformance and manipulation • Diverse XPS content • Correct rendering

  6. Key Test Tools • XPS conformance validation tool isXPS.exe • Print ticket conformance validation tool PTConform.exe • Automated Rendering Verification tool LooksGood.exe

  7. WDK Test Tools • XPS Content Library for printing • Conformant XPS content from diverse producers • Not conformant or invalid XPS content • Security/penetration tests • Corrupted XPS content • Corrupted PrintTickets • DEVMODE Corruptor

  8. WDK Test Tools • Print driver stress • Windows Presentation Foundation (WPF) printing test tools • WPF rendering test • WPF stress test • 2007 Office system content rendering test • Other XPS content rendering test • XPSDrv Filter test daemon

  9. WDK Test Tools • Functionality tests • Driver configuration tests • PrintTicket test • GDL Checker • Print Device Capabilities • DocumentProperties test • Driver or printer device rendering tests • PGremlin and PGremlin2 rendering tests • Print Area test • Photo Print test • Cancel Job test

  10. Test Tools Summary • Easy to use test tools are available now • They cover a wide range of test areas • XPS and PrintTicket conformance tools are critically important

  11. XPS Conformance And isXPS Justin SloneTest Development EngineerDigital Documents Platform and Solutions

  12. XPS Conformance • XPS conformance enabled through • Strict standard, strict test tools, strict implementations • isXPS.exe (codenamed isReach) is a strict test tool designed and developed by Microsoft • Assists in determining if an XPS document conforms to the XPS specification

  13. XPS Conformance Authority • In order of authority • The XML Paper Specification • The XPS conformance test provided by Microsoft • The WPF XPS Viewer

  14. isXPS Overview • Goals of isXPS • Verify Open Packaging Conventions (OPC) conformance • Verify XPS Document conformance • Provide detailed error information • Requirements to run isXPS.exe • .NET 2.0 • WPF

  15. XPS Document Framework DocThumb.jpg Legend Resource Parts – OPC Parts – XPS Parts – Conceptual Parts – Relationships – Markup References – Package Root _rels/.rels FixDocSeq.fdseq Image_1.jpg _rels/FixDocSeq.fdseq.rels _rels/.rels FixDoc.fdoc 1.fpage 1.fpage _rels/1.fpage.rels Package Root Font_0.ttf Image_1.jpg

  16. Conformance Checks DocThumb.jpg • Pre-validation • Validate font and image parts • OPC validation • Validate relationship markup • Process package relationships • Digital Signatures • Core Properties • Thumbnails • Etc Package Root _rels/.rels FixDocSeq.fdseq _rels/FixDocSeq.fdseq.rels FixDoc.fdoc 1.fpage _rels/1.fpage.rels Font_0.ttf Image_1.jpg

  17. Conformance Checks DocThumb.jpg • XPS validation • Start from fixedrepresentationrelationship • Validate markup of FixDocSeq • Follow <DocumentReference> to FixedDocs • Validate markup of FixDoc • Follow <PageContent> to FixedPages • Validate markup of 1.fpage • Discover Resource Parts Package Root _rels/.rels FixDocSeq.fdseq _rels/FixDocSeq.fdseq.rels FixDoc.fdoc 1.fpage _rels/1.fpage.rels Font_0.ttf Image_1.jpg

  18. Conformance Checks DocThumb.jpg • Markup references • Font references • Image references • ICC profile references • Resource dictionaries • Processing similar to a FixedPage • Process relationships from FixedPage part • Confirm that there are matching required-resource relationships to all markup referenced parts Package Root _rels/.rels FixDocSeq.fdseq _rels/FixDocSeq.fdseq.rels FixDoc.fdoc 1.fpage _rels/1.fpage.rels Font_0.ttf Image_1.jpg

  19. Most Used Switches -f=<FilePattern> The file on which to perform the validation e.g. file.xps or *.xps /s Apply FilePattern to all subdirectories -logger:<LogType> The logger to use (File, Console, WTT) -logfile:<LogFile> The log file to write to when using the File logger Default logfile is “isXPSLog.txt” Most Common Usage

  20. isXPS Logfile Sample Error Log Rollup +Start Test: /Documents/1/Pages/3.fpage Markup Info: Validating Markup of Part 3.fpage using target namespace … Fail: Markup is not Conformant: Number of errors: 1 Info: Error #1: At position (4,93) Message: The ‘Stretch’ attribute is not declared. -End Test: /Documents/1/Pages/3.fpage Markup Result: Fail -End Test: Processing file: C:\Exercise_1.1.xps Result: Fail -End Test: isXPS Result: Fail *********Log Rollup************************************************ TestName: isXPS PassRate: 81% Pass: 18 Warn: 0 Fail: 4 Block: 0 ******************************************************************* Result: Fail

  21. isXPS Takeaway • Use isXPS.exe for easy OPC and XPS conformance validation • Detailed error information helps quickly isolate bugs • Visit the XPS Printing hands on lab • XPS Testing and Conformance lab • Find isXPS (named isReach) in Beta 2 WDK and SDK

  22. XPS Test Strategies Jim ZuberXPS Test ArchitectQualityLogic, Inc.

  23. QualityLogic, Inc. • De facto standard test tool provider to printer industry for 20 years • Released XPS test suites to the industry in late 2005 • Provided XPS training to over 20 XPS early adopter companies • Just completed a set of XPS analysis and debugging utilities

  24. Topics • XPS Characteristics • Keys to Interoperability • Testing Challenges • XPS Consumer Analysis

  25. XPS Characteristics • Standards based • XML, JPG, TIFF, ICC, Etc • Clear specifications • Example code • Clarifications • Baseline reference • XPS Viewer

  26. XPS Characteristics • A very efficient set of drawing primitives • Paths can contain arcs, lines, and Bezier curves • Paths and Glyphs can be painted with brushes • Common properties control clipping, transforms, and opacity

  27. XPS Characteristics • Simple syntax • Elements and attributes • Low complexity • Human readable • A very testable technology!

  28. Keys To XPS Interoperability • Clean XPS markup generated by XPS producers • IsXPS • PTConform • Conformant XPS consumers • Functional Test suites • Comprehensive Test suites • Minimize specification ambiguities • Xpsinfo @ microsoft.com

  29. Keys To XPS Interoperability • Application compatibility testing of XPS consumers • All print paths • Key applications • Diversity of producers • Conversion programs • Strict de facto standard XPS consumer • WPF XPS Viewer • Practical arbiter of “is it right”

  30. XPS Testing Challenges • Clarifications to specification still emerging • No hardcopy reference target • Page comparison • Practical implementation limits • Few unique XPS producers • Interoperability testing • Usage models

  31. XPS Testing Challenges • Interactions between XPS markup and PrintTickets • Complex scenarios with VisualBrush • New image file format • WMPhoto • XPS analysis • Interleaved files

  32. XPS Analysis Tools • Microsoft • XPS Viewer • IsXPS • PTConform • XamlPad • QualityLogic • StatGen • PrintTicketer • XPS Parts Assembler

  33. XPS Consumer Analysis • Identify the symptoms • Is it a crash or a visual anomaly? • Do you get an error report? • Try viewing the file in the XPS Viewer • Does the same error occur? • Get a big picture view • Unzip – What parts are in the package? • Statistics – Stream sequence and element usage

  34. XPS Consumer Analysis • Schema Validation • Microsoft’s isXPS program will quickly validate the schema, as well as relationships and resource file integrity • Test Code Fragments • If problem also occurs in XPS Viewer, cut and paste suspect markup into XamlPad to isolate problem

  35. XPS Consumer Analysis • Problem occurs only in device under test • Use ZIP utility and XML Editor to modify the XPS markup in the container • Reduce to smallest number of XPS elements that reproduce problem • Suspect PrintTickets • Extract PrintTicket part and run PTConform to find syntax problems • Use PrintTicket editor to modify PrintTicket settings inside container to isolate problems

  36. Summary • XPS has the potential to quickly achieve a high degree of interoperability • Tools are available NOW to start testing and debugging your XPS implementations

  37. Call To Action • Familiarize yourself with XPS and PrintTicket specifications and XPSDrv technology in particular • Use Microsoft test tools to validate your implementations • Be ultra strict as far as XPS and PrintTicket conformance is concerned • Test for compatibility now! • Test the GDI Print Path, XPS Print Path, and compatibility paths • Test your company’s XPSDrv and XPS-capable printers • Report problems immediately • Invest in testing – it pays out!

  38. Call To Action • Understand your company logo goals and review new logo requirements • Basic and Premium • At WinHEC • Practice driver dev and testing skills in XPS Printing hands on labs • Ask the Experts at lunch today • Visit the Microsoft Pavilion to see XPS demos • Attend related sessions • PRI050 Inside Printer Installation on Windows Vista • PRI039 Using the Windows Color System in Device Drivers • PRI102 Using XPSDrv Print Drivers to Extend Windows Print Functionality • PRI019 Developing XPSDrv Print Drivers • PRI115 Windows Media Photo: A New Format for End-to-End Digital Imaging

  39. Additional Resources • Web Resources • Application Verifier: http://go.microsoft.com/fwlink/?LinkId=52529 • XPS Portal http://www.microsoft.com/xps • Links to relevant blogs, whitepapers, specs • WHDC Printing documents http://www.microsoft.com/whdc/device/print/default.mspx • Windows Digital Documents Platlform Team Newsletter https://profile.microsoft.com/RegSysProfileCenter/subscriptionwizard.aspx?wizid=77d9786e-9500-40a4-ba20-a4c7504d83ca&lcid=1033 • Technical advice • WDK and SDK • QualityLogic http://www.qualitylogic.com • Web Resources • QualityLogic XPS Test Suites and Tools: tools@qualitylogic.com • QualityLogic XPS Training: http://www.qualitylogic.com/xps/training.html • E-mail XPSinfo @ microsoft.com Prninfo @ microsoft.com info @ qualitylogic.com

  40. © 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related