Test automation and software craftsmanship

Benjamin Bischoff, Test Automation Engineer (SDET) at trivago N.V. (ex Ubisoft)

This is a new entry in the series "Magic principles in test automation". Today, I will cover the topic of repetition. To read the last one, please check out Magic principles in test automation: Misdirection.

Our current test automation setup for end to end testing is using Maven for preparing the test data, running our test scenarios and creating a test report. Recently, I wanted to refactor the way we use Maven's lifecycles and found a surprisingly easy way to do just that.

This is a new entry in the series "Magic principles in test automation". Today, it is about direction and misdirection. To read the last one, please check out Magic principles in test automation: Clarity.

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.