July 2003
Intermediate to advanced
608 pages
16h 15m
English
In the last two chapters, we looked at the way in which much of the value of testing is delivered to the project team. Bug reports give the project team a tangible opportunity to improve system quality, or to at least take appropriate steps to deal with known bugs when they hit the field. Results reporting lets management know that some risks are perhaps lower than expected—i.e., some tests were run that passed—and gives managers useful overall information to guide the project to success.
This chapter is about how we testers keep adding value to the project as the project evolves and changes.[1] After all, on most projects, we're not going to ship or deploy the ...