Classic Testing Mistakes

I have two goals for this paper. First, it should identify the mistakes, put them in context, describe why they’re mistakes, and suggest alternatives. Because the context of one mistake is usually prior mistakes, the paper is written in a narrative style rather than as a list that can be read in any order. Second, the paper should be a handy checklist of mistakes. For that reason, the classic mistakes are printed in a larger bold font when they appear in the text, and they’re also summarized at the end.

[1]  Cem Kaner,et al.  Testing Computer Software , 1988 .

[2]  Jeffrey M. Voas,et al.  Predicting where faults can hide from testing , 1991, IEEE Software.

[3]  Cem Kaner,et al.  Testing computer software (2. ed.) , 1993 .

[4]  Michael Friedman,et al.  Software Assessment: Reliability, Safety, Testability , 1995 .

[5]  John D. Musa,et al.  Software reliability measurement , 1984, J. Syst. Softw..

[6]  John D. Musa,et al.  Software reliability - measurement, prediction, application , 1987, McGraw-Hill series in software engineering and technology.

[7]  Jakob Nielsen,et al.  Usability engineering , 1997, The Computer Science and Engineering Handbook.

[8]  Geoffrey A. Moore,et al.  Crossing the Chasm , 1991 .

[9]  Michael R. Lyu,et al.  Handbook of software reliability engineering , 1996 .

[10]  Brian Marick,et al.  The Test Manager at the Project Status Meeting , 1997 .

[11]  Michael Dyer.  The Cleanroom Approach to Quality Software Development , 1992, Int. CMG Conference.

[12]  Brian Marick,et al.  The craft of software testing , 1994 .