No matter what the domain or company, there are some common problems that always tend to affect new automation projects. Here are six top reasons automation projects can fail. Keeping these pitfalls in mind will help you to avoid them and instead build stable automation frameworks, making the endeavor a collaborative experience so that your whole team owns automation.
It's been suggested that because automation can only do checking, automation cannot learn. But if you're talking about the acquisition of knowledge through experience and study, Jeremy Carey-Dressler believes automation can, in fact, learn—with a tester adding some additional code to capture and analyze more available data.
Max Saperstone, director of test and automation at Coveros, discusses the different types of tests that Selenium helps with, as well as why Selenium is very fragile. He also gets into the testing pyramid and how the layers of the pyramid work break down, the distinction between testing and checking, and which tests developers should be responsible for.
Chris Loder, an automation architect at InGenius Software, talks about his open source framework for automation, as well as why he says he left testing behind and started automating. He also discusses running the Test Lab at STARWEST, where conference attendees can practice their QA skills together to solve puzzles and test code. This year there were new AI features and an Automation Zone, where participants got hands-on experience with automation.