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.
Β
Better than a generic video, see YOUR test, live, ready to show you what matters most: quality at scale.
Explore MoT
QALS Summer 2026: a leadership summit to move beyond AI testing pilots and build production-ready, AI-first QA organizations - powered by the BrowserStack AI Test Platform and 25+ connected AI agents
Unlock the essential skills to transition into Test Automation through interactive, community-driven learning, backed by industry expertise
Debrief the week in Quality via a community radio show hosted by Simon Tomes and members of the community
Comments