Agenda

I’ve asked myself this question numerous times, I’ve trained myself to do so, because I understand its importance. However, I’m often left baffled by colleagues and other testers who reject the idea of deleting a test. Why do they find it such a scary concept?

So the result is that we continuously look and review the same tests, not knowing if they’re mitigating any risks, or worse, not knowing what they are testing anymore. But if you’re like me, you’ve probably looked at some failing tests before that left you thinking “why does this even exist?!”. That trigger is one you shouldn’t ignore.

In this talk, I’m going to share my experiences of listening to this trigger, but more importantly, I’ll explain the actions I take. You’ll learn how to analyze the full lifecycle of an automated test to truly understand its value. We’ll talk about the total cost of ownership of a test, and how it is a key analysis factor when attempting to reduce feedback loops. I’ll bring some stories from the company I work for to support this. After all, we’ve gone from automated regression environments running thousands of tests overnight to a CI/CD reality.

I love my delete key, I hope to share the love!

Having a bigger team of testers who have the characteristic of writing code can be pretty painful when the tester will change the team or even worst leave the company. Maintenance is difficult even when the tester is still on the team since he has duplicated the same logic in a huge amount of page objects which will be almost impossible to be refactored in a very short period of time. Pattern Object Model helped us to gain the trust of new clients by delivering automated tests on day one of the projects and regain the trust of existing clients by reducing the maintenance time. 

Tutorials and resources available can teach you the tools but they rarely cover the best practices. I will talk about the most common errors and anti-patterns  in performance testing and how you can avoid them - from tool selection, through test design, up to tester's development. 

They are called the “black-boxes” and literally represent a box with an Arduino inside. Using the help of unsuspecting volunteers we’ll let them figure out how each box works and demonstrate that to the audience. This talk will showcase some key biases that we have in our human brains and why it is important to avoid them. Hint: these biases don't make it easier for us to be working as testers!

We explore testing models, tools, and best practices to establish a robust automation testing strategy, with a particular focus on the significant benefits of mocking and stubbing. Join us as we uncover the vital elements of thorough web application testing and guide you toward delivering high-quality web solutions.

The impact of this on testing will be large. For a large part, well-known approaches will still be sustainable. Organizations as well as testers will also have to adjust to keep up with the times. Sometimes it is hard to keep up and still need to start with testing. The 2 approaches helps to provide initial insights.

This presentation discusses two low-level approaches, The Auditors Approach and The Blackhole approach.  These are suitable for use in organizations where knowledge and resources related to AI/ML are still limitedand yet can be integrated into existing test approaches. The Auditors approach and the Black hole approach to be introduced here.

These two approaches can help testers to gain new knowledge in a simple and wild way in the short term. And soon better to understand the all-embracing approaches that are yet to be developed.