You’re tasked to work on an existing test automation suite, and you note usual problems:
– Slows down the development process
– Test addition is an afterthought in the dev cycle
– Doesn’t point to the problem area in code on failure
– Doesn’t actually give you regression confidence
– Rely on just one person to fix or run it (you!)
– Tests get or “are tagged to be” ignored

You need help. And the help you need is not creating a new framework, but rather learning to tidy it up so that instead of problems, your tests spark joy.

In this talk, we learn to implement rules/techniques to achieve test atomicity, efficient DOM structure naming for tests, tagging XHR calls, the folder structure for better readability and “what tests to keep” rather than decide “what tests to discard” to keep your suite clean, lean and mean. You’ll learn that your tests, like mine, can spark joy