How We NOW Test Software at Microsoft
- 2. ! ! !!!!! ! !!!! Alan Page is a principal SDET—a fancy name for tester—on the Xbox console team at Microsoft. Edging up on twenty years in software testing, Alan has previously worked on a variety of Microsoft products including Windows, Windows CE, Internet Explorer, and Office Lync. He spent some time as Microsoft’s director of test excellence where he developed and ran technical training programs for testers throughout the company. Alan was the lead author of How We Test Software at Microsoft and contributed chapters on large-scale test automation to Beautiful Testing and Experiences of Test Automation: Case Studies of Software Test Automation. You can follow Alan on his blog or on Twitter @alanpage.. Alan Page Microsoft
- 6. 5/18/15% 4%
- 8. 5/18/15% 6%
- 9. 5/18/15% 7% Nobody’s$Perfect$ 1) In the intro, I state that Ken approached me in the fall of 2007. On reflection, it was actually late fall 2006. I began writing the first chapter in January 2007 (chapter 4 to be exact). Minor issue, but an Author Bug nonetheless. 2) The table on p. 19 is missing a line between USA (California) and Hyderabad (Production Bug) 3) On page 95, where the header says. “3BV”, it should say “3BC” 4) There's a bit of weirdness with the code coverage data on page 119. Bj explains it in detail on his blog here. (Author bug) 5) On page 120, the explanation refers to variables names myString and myCharacter – but we use different variable names in the code (s and c). (Author Bug). 6) On page 123, the title of figure 5-6 is incorrect (the function is SimpleGetNT5ClientVersion). 7) On page 125, the text refers to the Int.Parse() function, but it doesn’t exist in the code fragment (oops - Author Bug) 8) On page 202, the text reads “Total fixed found / total bugs fixed”, but it should read “Total bugs fixed / total bugs found” 9) On page 221, the “Positively False” sidebar is not a sidebar, and in fact the box around it encompasses the additional points (Supported platforms, Complexity, and Other factors) and section (We don’t have time to automate this) that aren’t part of that sidebar (Author Bug) 10) On page 226, the sample using InvokePattern could use some more documentation (Author Oversight) 11) In the code sample on the bottom of page 235, I have mismatched quotes in two of the lines. (Author Bug).
- 10. 5/18/15% 8%
- 12. 5/18/15% 10% Senior%Vice%President% GM%or%VP%of%Dev% Dev%Managers% Architects% GM%or%VP%of%Test% Test%Managers% Test%Architects% GM%or%VP%of%Program% Mgmt% PM%Managers% Etc.% Vice%President% Engineering%Manager% Engineering%Manager% Engineer% Engineer% Engineer% Engineer% Engineer% Engineer% Engineer% Engineer% Engineer% Engineering%Manager%
- 15. 5/18/15% 13%
- 17. 5/18/15% 15%
- 18. 5/18/15% 16%
- 20. 5/18/15% 18%
- 21. 5/18/15% 19%
- 29. 5/18/15% 27% “That’s the way we’ve always done it.” “That won’t work for us.” “We tried that once, and it didn’t work.” Things%I%Hear…%a%Lot% “The old way won’t work here because….” “This can work for us, because…” “This will work for us, because…” Things%I%Say…%a%Lot%
- 31. 5/18/15% 29%