The other days I was reading about the top 10 reasons why test automation is flaky which I found very true and perhaps the most spread in my experience.
The article made me think of all the projects I’ve been involved and what were the challenges I faced. I must say that no test automation approach was easy. Some of them were rewarding, others were good enough, while others successfully failed.
So, in addition to the initial top 10, I put together another 10 challenges I constantly face when dealing with test automation effort. My overall conclusion before jumping to the list is:
“The beauty of test automation consists in the challenges we face”
- Creating a test automation team isolated from product team
- Not using widely spread patterns
- Automate a product which was not designed for that
- Expecting one automation framework to fit all sizes, all situations
- Not being able to say NO
- Test automation owned only by testers and not involving the team in the effort
- Not getting development’s commitment to support automation
- Just because is TEST automation, does not mean it is solely a TESTER’s responsibility to do it
- Not using test automation results to guide your testing activities (as Richard Bradshaw mentioned in a recent video: every failed test is an invitation to explore).
- Using the test pyramid to guide your testing efforts (see: John Stevenson post where he presents a different view of the pyramid model)
What are your challenges?