There are lots of “best practices” for test automation, like the Test Pyramid, Page Object Model, Layered frameworks, and the list goes on. Despite this, test automation initiatives often fail to deliver the expected results. This is a problem!
To add to this mystery, there are also lots of test automation specialists, but yet, sometimes you come across people who don’t even know why they need test automation on their own project.
It turns out, that there are (at least) two different schools of Test Automation: test automation as a way to assure quality and test automation as a way to drive development. But in real life we always want something in the middle. I want to take this less-trodden middle path with you.