ABSTRACT
I am not talking here about taking on your least favorite developer (or programmer). I am talking about getting developers to test the soware or code that they write.
is chapter has attacks that many testers think should be “owned” by the developers. Some developers think that all testing is owned by a “test group.” ese views are at odds. Ownership implies responsibility. e team owns the qualities of any product. erefore, if a developer runs the attacks of this chapter, nds their own bugs, and xes them, then the quality of the product is improved. In many cases, the developers are busy or otherwise unable to run the attacks found in this chapter. In this case, an alternate option is to have someone independent from the developers conduct these attacks-as long as they have access to the code. It should not matter who runs the attacks of this chapter as long as the attacks are run and resulting bugs xed, the result of which is to produce a better-quality end product.
