如何在不可能的期限内完成无文档的软件测试.pdfVIP

Testing Undocumented Software Under Impossible Deadlines Cem Kaner, Ph.D., J.D., ASQ-CQE Star 99 East Introduction Introduction I didn’t come up with the idea for this talk--the STAR folk suggested it as something that I might be able to provide a few insights into. After all, this is a chronic complaint among testers. . . . Well, here goes. How should you deal with a situation in which the software comes to you undocumented on a tight deadline? I think that the answer depends on the causes of the situation that you’re in. Your best solution might be technical or political or resume-ical. It depends on how you and the company got into this mess. If it is a mess. Copyright (c) Cem Kaner 2 What Caused This Situation? What Caused This Situation? So, let’s start with some questions about causation: • Why is the software undocumented? • Why do you have so little time? • What are the quality issues for this customer? Copyright (c) Cem Kaner 3 Why Do You Have So Little Time? Why Do You Have So Little Time? A Few Possibilities • Time-to-release drives competition • Cash flow drives release date • Key fiscal milestone drives release date • Executive belief that you’ll never be satisfied, so your schedule input is irrelevant • Executive belief that testing group is out of control and needs to be controlled by tight budgets • Executive belief that you have the wrong priorities (e.g. paperwork rather than bugs) • Executive belief that testing is irrelevant • Structural lack of concern about the end customer, or • Maybe you have an appropriate amount of t