Presentation abstract

Old habits are hard to change. This also stands true when adopting ATDD/TDD practices. One of the main reasons for ATDD/TDD relatively slow penetration is the so called need to first make the production codes fit specific design patterns, or in other words design the code for testability. However, in today’s world of testing tools, there is no true need for these changes to occur. Isolation frameworks have grown beyond the need to refit the code to their needs and are able to isolate any part of any given design.

A major part of the community is advocating that these kinds of design changes are beneficial, while this may hold true, it is not relevant to any real testability issues. If these design patterns makes a better design, please take it up with the design “department”. Don’t make a testing issue out of it. Presenting redesign as a prerequisite for test automation, add another significant barrier for most companies out there. This talk will demonstrate how one barrier on your way to happy TDDing can be removed using the proper tooling, and prove once and for all that Design For Testability is not much more than a fraud.

About the speaker – Lior Friedman

Lior Friedman (imistaken.blogspot.com),  is a full-fledged Agile Coach and co-founder of Practical Agile. With more than 15 years as an IT professional,  he promotes agile values helping companies adopt these principles and adapt such practices into their own local context. After leading the development of cutting edge testing tools at Typemock Ltd. and helping numerous companies with their TDD implementation; he currently provides training, mentoring and high end consulting services to clients, (specializing in AUT, TDD and general agile transitions)