Define Every Team Member’s Testing Role
It’s too easy for developers to think their job is restricted to designing and writing code. They don’t see a need for testing along the way. If you don’t care how good the code is, I can write all the code you need. In an afternoon. With one hand tied behind my back. But would that code work? Not a chance.
I bet you care whether the code works. And I bet your developers do too. Too many developers are unaware that when they write code they also write defects. The way to write fewer defects is to have continuous review of the work products and to find the defects faster.
If everyone is testing all the time, why do you need system testing? System testing helps the team see the problems that don’t appear ...
Get Manage It! now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
