focus on eliminating the test team, they focus on doing a more effective and efficient job of testing with the resources they already have.
And Context Matters, Too
The last two articles have run the risk of making you think that all the matters is testing prowess, picking the right techniques and tools. But that's not true. Context matters. When do we start testing? Who does the testing, and what makes them a fit? Does the test team understand where they fit into the project, and vice versa? In the next article, we'll look at the importance of context through a topic I call pervasive testing.
Bibliography
R. Black and G. Kubaczkowski, "Mission Made Possible," Software Testing and Quality Engineering magazine, Volume 4, Number 4.
C. Jones, Estimating Software Costs . McGraw-Hill, 1995.
C. Kaner, J. Bach, and B. Pettichord, Lessons Learned in Software Testing . Wiley, 2001.
D. Graham and M. Fewster, Software Test Automation . Addison-Wesley, 1999.
| Attachment | Size |
|---|---|
 Manual or Automated? | 20.58 KB |
Pages
About the author
Rex Black is President and Principal Consultant of RBCS, Inc., a consultancy that provides testing experts worldwide, serving clients such as Bank One, Cisco, Hitachi, IMG, and Schlumberger in consulting, training, and hands-on implementation. He has written Managing the Testing Process, Critical Testing Processes, and numerous articles, along with presenting papers and keynote speeches at international conferences.
