What’s more important, production code or test code? Well, it’s clearly production code, which is why we have teams of people working on it. But, don’t we use test code to inform us about the quality of the product code? Indeed we do, that’s why it’s imperative we treat test code like production code, and that means following patterns and good practices.
Without clear design and implementation patterns, automation code will become unmanageable. This leads to longer time to create new tests, fix tests and test execution - time most teams can’t afford to lose. It can also lead to brittleness, flakiness and false positives, that over time start to reduce the trust we have in our tests.
In this talk, the first session of our Automation Patterns deep dive, we are going to discuss why patterns are essential, and discuss the impact of not following them. We’ll provide examples of good patterns along with the fundamental principals they are built on. We’ll share common bad patterns we’ve seen, and provide better alternatives.
