Alexander Tarlinder

“These are some of the bigger issues the developer testing strategy needs to address, but there will be smaller ones too, which still need to be handled to avoid diverging implementations and misunderstandings. Here are some questions that may be helpful in reaching such an understanding: Which tests give bang for the buck and which don’t? What types of tests are we running and how do they overlap? What types of tests are we avoiding (and why)? How large should a test preferably be? (Size depends on the level of abstraction too.) How many layers is a single test allowed to touch? Do we optimize for speed of execution or test simplicity? How do we handle test data and its setup? How do we approach integrations with external systems? What testing frameworks and libraries do we use? What trade-offs are we willing to make in the spirit of working with legacy code?”
― Alexander Tarlinder, Developer Testing: Building Quality into Software (Addison-Wesley Signature Series