A Testable Architecture - how can you ensure that the architecture you are implementing is testable?

An application can only be tested successfully using test automation and executable specifications if the architecture is testable. The tests must be fast, reliable, and offer good diagnosis precision. They must also be easy to write, maintain, and execute. Tests without these properties will be abandoned and the effort creating them will be lost.

In this session you will see one battle proven example where I have used executable examples and ended up with a testable architecture as well as living documentation.

Takeaways

* With the proper approach, ending up with a testable architecture is doable and fun
* Outside-in development supports test automation
* Re-using executable examples is not too hard when it is implemented properly