Since I have been an amateur magician for the last 34 years, this subject naturally influences my thinking on software. This post will kick off a little series on magic principles in relation to test automation.
Recently, I read a Tweet by Maaret Pyhäjärvi concerning the value of test automation. She claimed that "Lack of test automation moves known knowns to unknown knowns."
I strongly agree because if you don't have automation in place to "remind" you of known issues that might come up again, you will forget about them. In my view, test reporting plays a strong role in this as well.
Lately, I have been thinking about the old discussion about the purpose, pros and cons of automated tests.
There are different opinions when it comes to test automation and I will try to break them down one by one.
A little disclaimer first: this is not about bragging! I would just like to take the oportunity to tell you a little bit about my journey into test automation. In fact I presented this during the Nordic Testing Days 2019 conference in Tallinn, Estonia.
At trivago, we are using an in-house developed Selenium framework based on cucumber-jvm to run automated browser tests. As the test suite increased (the time exceeded 45 minutes for a full run), we were looking for ways to move away from sequential towards parallel execution.