1. James A. Whittaker Software Architect Visual Studio Team Test Microsoft http://blogs.msdn.com/james_whittaker jw@microsoft.com

9. Global climate change

10. Alternative energy

11. Managing global finance

13. “A second V-22 crash in December 2000 killed four Marines. The accident was pegged to a ruptured hydraulics line and a software failure.” - http://community.seattletimes.nwsource.com/archive/?date=20030226&slug=osprey2 6 http://community.seattletimes.nwsource.com/archive/?date=20030226&slug=osprey2 6 “Fans of the rock band Pearl Jam got a taste of cyber-gridlock Saturday, when a software failure disabled phone lines set up for ticket requests for shows in Seattle, Toledo, Ohio, and other cities.” - http://community.seattletimes.nwsource.com/archive/?date=19960814&slug=234416 1 http://community.seattletimes.nwsource.com/archive/?date=19960814&slug=234416 1 “Patriot Missile's Tragic Failure Might Have Been Averted -- Computer Glitch Probably Allowed Scud To Avoid Intercept, Army Says” - http://community.seattletimes.nwsource.com/archive/?date=19910815&slug=130007 1 http://community.seattletimes.nwsource.com/archive/?date=19910815&slug=130007 1 “Software Failure Halts Big Board Trading for Over an Hour” - http://query.nytimes.com/gst/fullpage.html?res=9C05E0D7173EF93AA35755C0A9679 C8B63&scp=1&sq=%22software%20failure%22&st=cse http://query.nytimes.com/gst/fullpage.html?res=9C05E0D7173EF93AA35755C0A9679 C8B63&scp=1&sq=%22software%20failure%22&st=cse “This is what happened in 2003, when a software failure near Toledo, Ohio, combined with sagging power lines and a simple error by a control room worker to cause a blackout in eight Northeastern and Midwestern states and Ontario.” - http://www.nytimes.com/2007/07/08/opinion/nyregionopinions/08CIperrow.html?_r= 1&scp=14&sq=%22software%20failure%22&st=cse&oref=slogin http://www.nytimes.com/2007/07/08/opinion/nyregionopinions/08CIperrow.html?_r= 1&scp=14&sq=%22software%20failure%22&st=cse&oref=slogin “Nike last year had to reduce prices and fly some products to customers after a software failure resulted in excess inventory and missed shipments.” - http://query.nytimes.com/gst/fullpage.html?res=9407E2DB133EF93BA15755C0A9649 C8B63&scp=24&sq=%22software%20failure%22&st=cse http://query.nytimes.com/gst/fullpage.html?res=9407E2DB133EF93BA15755C0A9649 C8B63&scp=24&sq=%22software%20failure%22&st=cse

16. fee = 8.95 fee = 0.00 fee = -100.00

25. The future I see Moving Test Forward Visualizat ion Test Culture Testing’s Butterfly Tests Ship with Product Informa tion Virtualiza tion Test Sourcing http://blogs.msdn.com/james_whittaker

26. For testers, it’s everywhere – On your desk – On your drive – On your network – In your head – In other people’s heads – … We need information to be available, actionable and alive

28. The future I see Moving Test Forward Visualizat ion Test Culture Testing’s Butterfly Tests Ship with Product Informa tion Virtualiza tion Test Sourcing http://blogs.msdn.com/james_whittaker

29. Hard problems: – Ain’t got no repro – The Vista lesson Solution: – Control the environment – Easier said than done … until now

30. Virtualization for user machines – Think Watson … only better – Fool proof debugging – Libraries of virtual test machines Virtualization for tester machines – Virtualized test libraries, just add apps – Environment-carrying tests

31. Virtual test machines would have value – Buy them, sell them, rent them Testers no longer test, they design – Determining what needs to be tested supersedes how to test it – Why select among tests when you can have them all? The result – Apps released after centuries of accumulated testing against hundreds of thousands of possible environments – Most apps don’t require dedicated QA staff

32. The future I see Moving Test Forward Visualizat ion Test Culture Testing’s Butterfly Tests Ship with Product Informa tion Virtualiza tion Test Sourcing http://blogs.msdn.com/james_whittaker

36. Well, there’s: – Input – Output – Data flow – Control flow – Modules – Dependencies – Environment variables – Files – Interfaces – Bugs

37. I’ve painted my vision of the future A future where – late cycle heroics are cause for shame – testing is thorough, predictable, repeatable – software just works – quality is an expectation – innovation is an epidemic

38. 20 years from now – Will the quality of software be taken for granted? Will users be genuinely surprised when it fails? – Will researchers look back in wonder that there was ever even a need for dedicated bug finders?

41. James A. Whittaker http://blogs.msdn.com/james_whittaker jw@microsoft.com