What's that Smell? Tidying Up Our Test Code - Angie Jones
You Can Become a Toolsmith Too! - Matthew Bretten00:30:01
Of Spies, Fakes and Friends - Help Your Code Lead a Double Life! - Rabea Gleissner00:27:39
Digging In: Getting Familiar With The Code To Be A Better Tester - Hilary Weaver-Robb00:45:41
Scalable XCUITests within iOS Pipelines - Shashikant Jagtap00:43:40
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.
Key takeaways include how to:
- Identify code smells within test code
- Understand the reasons why an approach is considered problematic
- Implement clean coding practices within test automation