An application can only be tested successfully utilizing test automation and executable specifications if the architecture is testable. The tests must be fast, reliable, and offer good diagnosis precision. They must besides 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 1 conflict proven example where I have utilized executable examples and ended up with a testable architecture as well as surviving documentation. Takeaways
- With the appropriate approach, ending up with a testable architecture is doable and fun
- Outside-in improvement supports test automation
- Re-using executable examples is not besides hard erstwhile it is implemented properly
