 Okay, come on. Let's get started. Hi everyone, my name is Oren and I'll talk about statistical element locators and Why what I think is currently missing in Selenium or why I think This should be added to the Selenium So in the last 20 years I've done a lot to help developers Tests to write their code. I've done how to overifications I've worked at up to two sides that you almost might know and I'm working on Having better selectors that can speed up no more flaky tasks. That's my goal for the next a year or two You have no more flaky tasks. So I want in this session. I want to talk about Why am I why am I building what exactly are we building and how does it how do how will it help? every tester and developer out there to do his job much better and and And we're gonna focus on one thing Which is which is the stimuli which is usually you set up for before any test you set up some data You do some actions and then you assert so we're gonna focus about mostly on the stimuli part and And that's the user interaction. That's what you guys know And this is something that unlike unit testing This is the part that the API which is actually the UI it keeps changing and Because it keeps changing We get tests that fail those false positives We want to reduce them to zero. So this is what we're gonna talk about. So On the stimuli side, we're gonna focus we're gonna drill down even more about how locators are building every click You find an element then you click it. So you have to find it first. So we're gonna look at that. We're gonna start Very softly. I know there's few that They're just beginners so we're gonna talk about few for a few minutes about how the browser and actually how Selenium how they Operate how they find elements there and then we'll move on and see how we can improve that so