Code smells occur in the source code of an application and can indicate deeper problems that are not apparent at first glance. Identifying and fixing these issues helps tremendously in securing and future-proofing the application under development and allows developers and testers to better understand, maintain, extend, and test the code.

In this session I will go through the different categories of code smells and explain each one with example code for each. Also, I will explain why it is good to know and be able to name different code smells even if you don’t do any programming yourself.

Most often, test frameworks are developed from scratch and gradually extended with the required functionality. This approach is perfectly normal, but carries the risk of creeping technical debt as well as poor maintainability, transparency and extensibility. These risks can be minimized by using clean software architecture.

In this talk, I will present two key parts of our internal Selenium-based end-to-end testing framework, which has been successfully used to test multiple web projects using desktop and mobile browsers during the past five years:

1. the plugin infrastructure using Java's Service Provider Interface
2. the custom WebElement decorator that enables more resilient Selenium WebElements

I will explain the rationale for using these architectural tools and how these approaches mean that we can still evolve this framework quickly and easily to meet new needs.

Having been a hobbyist magician for 34 years, I started noticing that some close-up and stage magic principles and theories don't only apply to magic tricks but also to software testing.

An example of this is the application of the KISS principle (Keep It Simple, Stupid) in software development. This helps to avoid unnecessary code complexity and make it easy to understandable and follow. In magic, this applies as well. Magicians strive for clarity and simplicity by creating effects that are easy to follow for spectators.

In this sessions, I will try to connect those two worlds and thus combine two of my passions. Also, I will try my best to illustrate the magic side of things with demonstrations. This is a challenge I set for myself - let’s see how it goes.

The ‘make’ command has been around since 1976 and was originally used to build executable programs. In this talk I want to show how this powerful tool can greatly reduce complexity and eliminate stumbling blocks of running your automated tests. This applies to both CI pipelines and local test runs on developer or QA machines.

Learn how the end to end tests for trivago's hotel search website are triggered, how we run them and what we do in terms of reporting and visibility of tests results. This is mainly about the technological aspects and challenges but will also touch on how and why we established certain processes.

This talk will touch on a range of topics like

• How the test automation team works at trivago
• What challenges we faced on our long way towards automated end to end testing
• How our complete test pipeline works
• Why we decided against some available frameworks and libraries