Test design is about bug-finding power. Test implementation is about not wasting time. We will discuss picking the right testing interface and choosing which tests deserve to be run more than once. After the tutorial, attendees will be able to apply three test design methods. They will also be able to articulate the economic tradeoffs of test implementation and automation. Presentation Format: Format will be lecture combined with short labs. Attendee Background: Attendees should be experienced programmers. No testing background is required. Examples will be in C++ or Java, but familiarity with any object-oriented language should suffice to understand them. Brian Marick worked for 11 years as a tester, developer, and line manager, mostly on operating systems and compilers. Joint research at the University of Illinois led to internal consulting and then, in 1992, to his own consulting business, TestingFoundations. Because practitioners are justifiably suspicious of those who talk about software development but never actually do any, he tries to spend half his time building, testing, and maintaining tools, some freely available. He is the author of The Craft of Software Testing (Prentice Hall, 1995) and the freeware code coverage tool (http://www.testing.com/tools.html). He was the first technical editor for Software Testing and Quality Engineering magazine and is now a contributing editor. His Web site may be found at: http://www.testing.com.
at a Glance |
|
of all Tutorials |
|