Software Testing Best Practices chillarege（软件测试chillarege的最佳实践）.pdfVIP

Copyright IBM Research - Technical Report RC 21457 Log 96856 4/26/99 Software Testing Best Practices Ram Chillarege Center for Software Engineering IBM Research Abstract: This report lists 28 best practices that contribute to improved software testing. They are not necessarily related to software test tools. Some may have associated tools but they are fundamentally practice. The collections represent practices that several experienced software organizations have gained from and and recognize as key. 1. Introduction Every time we conclude a study or task force on the subject of software development process I have found one recommendation that comes out loud and clear. We need to adopt the best practices in the industry. While it appears as an obvious conclusion, the most glaring lack of its presence continues to astound the study team. So clear is its presence that it distinguishes the winners from the also-ran like no other factor. The search for best practices is constant. Some are known and well recognized, others debated, and several hidden. Sometimes a practices that is obvious to the observer may be transparent to the practitioner who chants thats just the way we do things. At other times whats known in one community is never heard of in another. The list in this article is focused on Software Testing. While every attempt is made to focus it to testing, we know, that testing does not stand alone. It is intimately dependent on the development activity and therefore draws heavily on the development practices. But finally, testing is a separate process activity -- the final arbiter of validity before the user assesses its merit. The collection of practices have come frohm many sources -- at this point indelibly blended with its long history.