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 that production code is written with.
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 which is littered with several bad coding practices, we will walk through each of the smells and discuss why it is considered a violation and demonstrate a cleaner approach.
Β
With servers in >250 cities around the world, check your site for localization problems, broken GDPR banners, etc.
Explore MoT
What I learned about influence by becoming a stakeholder
Ascend to leadership roles by mastering strategic skills in automation strategy creation, planning and execution
Debrief the week in Quality via a community radio show hosted by Simon Tomes and members of the community
Comments