The way we test changes at breakneck speed - every few years, there are new tools, new techniques, and new buzzwords. Over the course of several decades, software testing has seen many effective practices and patterns.
Unfortunately, there are also practices or (anti)patterns that have more bad consequences than good ones despite initially appearing to be an appropriate and effective response to a problem.
Martin Fowler defines an antipattern as ”a solution that initially looks like an attractive road lined with flowers… but further on leads you into a maze filled with monsters.”
In this talk, we will share some antipatterns that we believe negatively impacted the testing community in the past - and what we are learning from those experiences.