Selenium 4 and the subsequent smaller 4.x releases have brought a few changes and a lot of great new features into the framework. We now have relative selectors for identifying page elements; the BiDi API/Chrome DevTools functionality to perform such tasks as emulating devices or capturing network requests; but there are also updates on how you can work with multiple windows or use the Actions API in your tests. I will show you all of these plus more to help you be up to date with the goodness of the Selenium framework.

Automation that works is something we strive to achieve and sometimes it is difficult to do. Tests fail randomly, and it is not easy to pinpoint the reason for failures. Or it is difficult to understand what a test is doing due to how it is written. Updating a failing test can be next to impossible. In some cases, tests are passing but there is obviously a bug they did not notice. These are all symptoms of automated tests that cannot help validate a feature or release without some manual intervention. What can be done about it? Let me tell you my perspective.

What really is the role of a tester? What activities can we perform on a daily basis, to help the company we work for achieve its goals? Should we focus only on finding and logging bugs? Or can we contribute with much, much more? Do we, as testers, see the whole picture, and are we as involved in the software development process as we could be? Do we shine and put in our best effort at work? 

In this talk I will highlight how many activities we, as testers, can contribute and provide valuable input to. Our product experience, talent and our analytical thinking can help shape requirements, speed up delivery, improve customer experience or improve faulty processes. We can make a difference in how we achieve quality in an organization by getting more involved. And in turn, all of this will help in our personal development and in us being recognized as highly skilled, amazing professionals.