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.
Β
Getting tests that catch real failures is the hard part. Watch the recording now on demand!
Explore MoT
Complex workflows, flaky tests, fragmented tools, and AI-driven pressure are making it harder for QA teams to keep up.
Elevate to senior test automation roles with mastery in automated checks, insightful reporting, and framework maintenance
Into the MoTaverse is a podcast by Ministry of Testing, hosted by Rosie Sherry, exploring the people, insights, and systems shaping quality in modern software teams.
Comments