Information Technology
Design Driven Testing
As program manager for ESRI’s ArcGIS mapping software product, Jim is responsible for a daily build of 20 million lines of code. He previously managed the transportation and logistics department for ESRI Professional Services, where he brought many multi-million–dollar software projects in on-schedule and on-budget using the design techniques described in this book.
Lots of people have many strong opinions on virtually all aspects of testing software. I’ve seen or heard of varied methodologies, systems, procedures, processes, patterns, hopes, prayers, and simple dumb luck that some code paths will never get executed. With all this help, we must have figured out how to ship outstanding rock-solid bug-less software, right? Yet, with each new release of the next great, most stable revision of our software products, test engineers still make that wincing face (you know the one), drawing back a little when asked, “Do you have the appropriate tests across the entire software stack?” The wincing exists because the truthful answer to that question is almost always: “I think so, but I don’t really know all the areas I should have had tests for.” And the software shipped anyway, didn’t it—bummer. This is job security for the technical support team, because the bugs shipped out will be coming right back to your team for the next service pack or emergency hot fix. We can do much better, and this book will show you how.
No copy data
No other version available