Be the first to like this
We are often reminded by those experienced in writing test automation that code is code. The sentiment being conveyed is that test code should be written with the same care and rigor with which production code is written.
However, many people who write test code may not have experience writing production code, so it’s not exactly clear what is meant by this sentiment. And even those who write production code find that there are unique design patterns and code smells that are specific to test code in which they are not aware.
Given a smelly test automation code base that is littered with several bad coding practices, Angie walks through each of the smells, discusses why it is considered a violation, and demonstrates a cleaner approach by refactoring the code live on stage.
Key takeaways include how to identify code smells within test code, understanding the reasons why an approach is considered problematic, and how to implement clean coding practices within test automation