Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Design For Testability - The good, the bad and the ugly

Given at Knetlik, by Gil Zilberfeld, it is a short presentation about what is design for testability, its uses and misuses.

  • Login to see the comments

Design For Testability - The good, the bad and the ugly

  1. 1. Design For TestabilityGood, Bad and Ugly<br />Gil Zilberfeld<br />Typemock<br />
  2. 2. Who am I?<br />Technical Evangelist at Typemock<br />In software development <br />for 15 years<br />Twitter: @gil_zilberfeld<br />
  3. 3. What is Design for Testability?<br />Create components ready for testing<br />TDD drives it<br />
  4. 4. Examples<br />Constructor injection<br />Factory Injection<br />Virtual by default<br />
  5. 5.
  6. 6. It’s Good Because…<br />You actually mean it!<br />
  7. 7. And it drives…<br />Decoupling<br />
  8. 8. But beware...<br />The misconception<br />
  9. 9. Design for Testability != Good Design<br />
  10. 10. It can get ugly…<br />Too many factories<br />
  11. 11. Testability is not a goal<br />
  12. 12. This is much better<br />
  13. 13. Questions?<br />Or contact me at:<br />gilz@typemock.com<br />Twitter: @gil_zilberfeld<br />Blog: http://gil-zilberfeld.blogspot.com<br />Typemock: http://www.typemock.com<br />

×