Test automation and software craftsmanship

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

Recently, Ministry of Testing asked about our favorite bugs ever on Twitter. So I thought this could be worth a blog post.

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.

In my open source projects (e.g. my Cluecumber Maven Plugin for Cucumber reports), I usually keep all the code in GitHub monorepos. This way, multiple projects that belong together are easier to maintain because you only need to checkout one repository instead of many.

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 use a Cucumber based framework for end-to-end tests of our most important web applications. Cucumber stores test result as JSON files which can be turned into human-readable test reports.

Up until now we used the widespread cucumber-reporting Maven plugin.

This is my talk from SeleniumConf 2017 Berlin about how the QA and test automation teams were set up for trivago's main product, how they used to work, and how we gradually introduced the test automation topic. This is not mainly about the technological aspects and challenges but more about how and why we established certain processes.