Joe Strazzere <strazzer@shore.net> writes:

"Early involvement by testing is critical. Not only do you avoid starting too late, but you also have a chance to:

• improve the ultimate testability of the product
• let the developer know that a bug has entered the system while the recent changes are still fresh in her mind
• have a better, ongoing, feel for the goodness of a system
• avoid some of the "we are delivering this code late, but we still want to ship it on time, so let's cut some testing out" syndrome.

I hate to see shops get into a "throw things over the wall" mode. Quality (and to some extent as you point out, testing) is everyone's job."

ecp@acm.org (Erik Petersen) writes:

"Re test designed before coding: Even before this, test team should be involved in review of design specs. This is the cheapest stage to fix bugs at, with design still at draft stage and easily altered. Often I have been on projects where the only people to look at the entire design document (other than the designers) are the test team, as programmers etc tend to only focus on their particular areas. All test leaders should have input to a design spec before it is signed off."

Got something to add?