Test-Driven Java Development, Second Edition - Second Edition

Documentation for non-coders

Traditional testers tend to form groups completely separated from developers. This separation leads to an increased number of testers who are not familiar with code and assume that their job is to be quality checkers. They are validators at the end of the process and act as a kind of border police who decide what can be deployed and what should be returned back. There is, on the other hand, an increasing number of organizations that are employing testers as integral members of the team, with the job of ensuring that quality is built in. This latter group requires testers to be proficient with code. For them, using code as documentation is quite natural. However, what should we do with the first group? What should ...