When done correctly, test automation is an excellent source of fast feedback for teams. When development check-ins are made, the automated tests are able to verify that the system is still working as expected. However, for many teams, what is supposed to be this reliable feedback mechanism is nothing more than unstable spaghetti code that requires constant maintenance.
A big reason for the instability of automation code is the lack of good design and architecture. Automation code should be written with the same care and consideration as production code if the team truly wants to see a return on their investment. However, because it is different than production development, it’s not always obvious how to accomplish this.
Join Angie Jones, as she discusses the four pillars of object-oriented programming, and explains how to utilize these concepts within test automation development.
Key Takeaways:
