Everybody’s talking about continuous learning and how essential it is for a tester. You have to keep growing, keep stretching yourself, keep exploring new worlds so as not to miss the forest for the trees. But how do you actually do that and grow on a daily basis? How can you become a better tester? And what about learning as a team, company, community?
Join this talk and hear the lessons I would have liked to hear 9 years ago when falling into testing. I will share my personal experience, pieces of wisdom I picked up on my way, as well as concrete tips on how to constantly reinvent yourself and the world around you. We are Groot!
In this tongue-in-cheek talk I will show how easy it is to disrupt or utterly ruin a test automation project. By describing seven proven methods to reach this end, I intend to give managers, testers and automators the means to recognize early on if their automation is in danger.
And by ‘warning’ against possible defences I will actually give them the tools to counter and solve such issues
I spent last couple of years performing, talking, writing and listening about software testing.
But what is software testing? I am told my job is to “break software”. But why break it, it looks good?! I like the programmers, they are my friends. And, as Michael Bolton says, “We don’t break software, it was already broken when we got it”.
I sure don’t break software for living, but I do something way better and much more satisfying - I break clichés about software testing.
So, my job as your guide in your journey in testing will be to break some clichés from the past in order to build the mindset of the modern tester.
The biggest issue when it comes to Selenium tests is attempting to interact with the page elements when they are not ready. Trying to click an element before it is available, trying to select a value from a dropdown when it is not yet populated, checking an element attribute before it is available - these are some of the most common reasons for failures when it comes to Selenium tests.
Such issues can be avoided by using the WebDriverWait Java class to redesign the way you interact with your page. In this talk i will show you how to get from click to click and wait, from select a dropdown value to wait and select, and so on.
I will show you how to replace your standard Selenium commands, like click, with customised waits that you can write to adapt to your test environment conditions. I will show you how to rethink your page interactions from a waiting perspective. And, as an added bonus, how you can replace some of the assertions you write with corresponding wait methods.