Most folks in the IT industry would agree that automation makes things easier. Folks would also agree that testing is needed to deliver quality products. Given that most of us agree on these points, the idea of automated testing should be a slam dunk.
The reality is that automated testing isn’t always a slam dunk. I frequently encounter leaders who question the value of automated testing, even after their organizations have invested considerable time and money into building frameworks and expanding automation coverage.
The reason for this skepticism toward automated testing is that it often fails. Here are four of the most common reasons I’ve observed that cause those failures—based on both successful and unsuccessful test automation projects—and how failure can be avoided.