Testing-Tools_ Print-ImagingDrvs.ppt

Testing And Tools ForPrint And Imaging Drivers Outline Basic testing philosophy Where Microsoft finds bugs What testing does Microsoft currently do Microsoft provided test tools Importance of Debugging Summary Basic Print and ImagingTesting Philosophy Test Device Drivers Right amount of QA before you ship Fewer bugs for users to find Lower support costs Quality not just the responsibility of QA team Need good tools for developers Enable developers to run unit tests Microsoft Investment Microsoft is interested in the test environment to improve the overall driver ecosystem Microsoft QA approach Inbox driver program Logo Program Provide tools for drivers we never see Driver education on tools and methods Where Microsoft Finds Bugs and How They’re Triaged Bug Buckets Main areas bugs are found (highest to lowest) Through code analysis (PREfast) Printable regions Basic printing features Stress testing Font handling Advanced features Setup Communications and I/O Microsoft supplies tools that target each bucket What Happens if Microsoft Finds a Bug? Reporting the bug What did you see? What were you expecting? Exact steps to reproduce Triage Is it in Microsoft code? Assign to a developer for investigation Fix Developer builds private for test to verify Ship team decides whether to accept the change to the product Check in Resolve Fix is verified against live build by test Tester who opened original bug is the only person allowed close the issue Microsoft Provided Test Tools Microsoft Testing of Printing and Imaging Device Drivers Tool Distributions Winparty 2005 Used for device and driver testing today Used for inbox driver check in Included in upcoming Windows Driver Kit (WDK) WDK Uses WTT Test Shell Makes it very simple for anyone to run tests and collect results What Architectures Are Supported? Tools work on a variety of architectures x86 x64 Itanium Inbox check-in requires testing on all three architectures by the IHV and Microsoft To test a 64bit operat