Testing: Saving the Best for Last
Lisa Crispin
Are projects moving too fast for your QA team? Is your QA team feeling stressed and overly busy? Are those darned programmers writing code that doesn't fit the frozen requirements, and ignoring those 10-year-old standards? Are product managers bugging you with last-minute changes? With the Waterfall method, this doesn't have to happen. In this tutorial, we will learn how QA teams can take control of quality at the end of the software development life cycle, and keep the programmers' buggy code out of production. This tutorial will help you, the QA engineer, learn to test quality right into that code at the last possible moment. You'll learn how to help get your project on a steady, slow pace, and be the hero who saves the day at the last minute. Using many hands-on exercises using Word, this tutorial will cover:
- How to produce an impressively thick test plan, suitable for clubbing errant programmers over the head
- Testing your test plan with Kent Beck's wordUnit
- Looking busy while waiting for the analysis, design and coding phases to complete
- Techniques to force programmers to follow standards
- Using entrance and exit criteria to slow down development cycles
- Testing quality into the code
- Strategies for lengthening the test cycle
- Keeping customers at arms’ length
- Tactics for isolating the test team for maximum productivity
- Top 10 Reasons to reject a build before you even test it
- How to know when you are done testing (look at the calendar, silly!)
Presenter Resume
Lisa Crispin is author of Extreme Testing: Compressing a Projects' Worth of Testing into a Six-Week Test Cycle (Addison-Wesley, 2006). She has overseen testing in Waterfall projects for Fortune 500 companies since 1982. Her most recent article in Better-Defined Software was "If Today's the Ship Date, I Must Be Done Testing."