 Nice theatrical and this is exactly what happened with Youth Packard Enterprise or what was once Mercury and the open source and the Selenium community. And I will guide you in today's presentation on how the market has shifted over the last 15 years, how everything looked like 15 years ago and how it looks like today. So a bit about myself, my name is Ory Bendedt, I've been with Youth Packard Enterprise software for the last 6 years. I started my career as a testing engineer, I was an automation engineer, I used a QTP, FIST and an internal tool, also Selenium for the last few years. And over the last year, after I've been a QA manager for 3 years, then I switched into the world in the world of product management and now lead a brand new offering later this year. I've been responsible for great products such as Youth Soap Runner and the QTP scorecard over my short term. So other than that, I'm Michael's father, I can promise you that over dinner we keep fighting about user experience. This is how for small talk later when we have time, then of course I'm a huge Star Wars fan, a certified Jedi master. I'm a huge San Antonio Spurs fan, one of the biggest in Israel, a Liverpool fan, any Liverpool fans here. Patriots fan in the NFL and of course this is me last week watching the Euro football with my hands. So this is about me and now let's start, let's get to business. And let's start with blowing up some myth about vendors, about enterprises, about cooperation and software testing. So first myth is that vendors such as Mercury and Youth Packard Enterprise only use their own tools. And I can promise you and you will see today that it's not about the tool. It's about finding the right tool for the right product. And this is the mantra that we have, although we tell all of our testing team, you must use news tea, you must use news tea. That's not how we do it. It's about finding the right product, the right testing tool for the right product. Myth number two, evil cooperation on the dark side, hate open source. And as you can see that we're here and it's kind of an irony and I saw some tweets about it during the day that the successor of Mercury and QTP is now sponsoring the Selenium Compact. And the fact is that we actually love open source. If you love open source, we love open source. And I will show you today how we are leveraging Selenium, Red Driver and the rest of the open source. Everybody does automated testing in our own way. Everybody is doing, but definitely everybody is using automated testing and I will show you exactly how it's being done. Let's take a walk down the history lane and let's go to a worldwide web long time ago and far, far away. Although it's not that long time ago and not so far ago. And let me take you to the days where the internet looked like that. The happy days of Web 1.0. This is actually the HP site. This is Amazon at the time of the project and they store all these images. And this is Microsoft and you want the most websites that you've ever visited. If you do, raise your hand. Yeah, okay. I can tell you my own personal website, the first one. It was spurs.com. This is exactly how it looked like. It took like seven minutes for it to load on my father's laptop. And I will never forget the moment after you know that. And this was my first website. And in that day, the testing tools looks exactly like that. This is the first version of beauty. It was called at the time. Let's fast forward to 2003. So this is inside me and this is Amazon. Some red Microsoft. And this is beauty people. This is how it looks. Some of it, I can promise you, still leaves the day. Fast forward to 2002 and talk about it in a second. This is Amazon. This is Microsoft. And this is QTP version. And as I said, during that time, there was a disturbance in the course. In the test automation course, which we now understand that is beauty. Yep, during those times, Selenium, it says July 9. And as I said, this could be part of it. And this is something that we see today. We see it especially in the context. So this was released almost standing here. It's time. And this is why we must have patience. And it took us time to understand that it's not about us versus them. But we can work together. It's not a battle anymore. But I'd like to point out the specific time that we understood that we need to shift our way of thinking. It was during the last year, the Microsoft announcement of edge support of WebPrivate. And at that time, I can promise you that the guys in Palo Alto started to spread from that point on. Everything changed with them. But let's see how we can start to show you the moment of chemistry. I started my career. I studied biochemistry. This is mercury. Okay, it's being used mostly into a thermal meter a while ago. Now it's too poisonous to be used. And selenium is being used mostly as an additive to the color of red. And the urban legend says that selenium is called selenium because it was supposed to be a cure for mercury poisoning. We're talking about the days of 2006, where QTP was probably the most dominant test automation tool. And that was the urban legend. And this is why selenium is called selenium. What I did over the last few weeks is the fact that I wanted to investigate to see whether this is effective. And the fact is, I'm very sorry, but it's not true. And it makes perfect sense today because there was little evidence in real research about the effect of selenium on mercury toxicology modifications. So it actually means that selenium is not the only question on the brief history. We are using selenium today. So we will start with something that for us is very obvious, but I had some discussions with the guys from Microsoft in Israel and they told me, what are you going to talk about? You're probably only losing. But for them, it was something else. So basically what we have is that we are building an automation framework on top of selenium. It usually uses between three and four layers. It really depends on the implementation. The first layer is the infra kind of the bare metal that works with the web driver and the locator. Every team calls it something. On top of that, we actually represent a model in the application. So it's user name, password and attributes. Some teams have their actions, which are small building blocks. So for example, they will decide that Login has an action that is called dologin or create user. And instead of writing the entire step, they just call the method that is called Login. And it performs. And of course, the last part is the tests that are complete end-to-end business flows that cover the entire application. The benefits of writing such framework on top of selenium, I'm sure that some of you are using that as well. So we are talking about reuse of testing assets of up to 50%. So we don't need to call anything on the back. We just have the framework. Of course, maintainability. So I don't need to copy and search in my code where I need to change my object in case something change. And the last thing, and when I was a QA manager, this was one of the most challenging things for me. I wanted to see how I can leverage my entire team, even the less technical and more business oriented testers. And this was the way that I was able to do. In my last role, I automated the Node.js Angular application. I had one automation engineering team and she was amazing. She did all the hard work and it allowed me to have 400% increase in the number of automated testing because she was the automation enabler for the rest of the team. So she was written up till the actions and then the rest of the team was completing the test in their own language and I will show you exactly how it's done. What I'm going to show you now is a list of products, real products that are currently being production, being used probably by some of you, and are being tested with Selenium. And these are real applications, no demo applications, real customer-sensing applications. So the Stomano load, if you've probably heard of load runner, is our cloud offering for performance testing cloud. And they are our most advanced automation team. They are writing the script in JavaScript, the testing JavaScript, and they are using Grunt and Jasmine to run everything. What they did is they have three layers of which is being developed by the automation technique. They have their containers, which can be developed by dev tester, software engineering test. And the last part is the actual test. Those are Jasmine files that represent a real business flow and these are being written by the entire testing team. So this is Stomano load and I will show you the test. So you don't see it but this is the intrap. If you want, just come outside the boot and I will show you the code. Here it says this is Protractor. So this is the first layer. This is Protractor. It also has some calls directly to the web driver. And this is again only being handled and maintained by the automation. The next part is the containers. It supports the different methods that it has. And again, this is developed by each dev tester that is being responsible for the system. The last part is the plane that the test is that easily run. This is Stomano load. And the next product that is being used is our latest ALM obtained, which is our next generation. Their test is being written in Java, fancy, but they started writing their code in JavaScript. TypeScript takes four layers of automation. They have the core intrap that talks to web driver and locators. They are doing that in one. They have the entities or the small ending block. And the last part is the test that are being written. Okay, again, so this is the core. The last part is the test that is almost in C. So it has a UI and write and extend. So this was ALM obtained and Stomano found. The next product is one of the most complicated products in common testing. So you can run it as part. The amount of technology. So you get the truth line sidebar here. This is JavaScript. Okay, you have the truth lines toolbar, which is also JavaScript. You have the Firefox browser because the Firefox browser. We have the status pane, which is how complicated it is to test these kinds of applications. So what we did is we decided to go outside and we used the application model from the with Selenium. So we are handling the JavaScript model with the web element with Selenium. So you can see that the launcher is WTF, the browser. And as I said, the state of mind for us changed. And this was the first time that Dinefstein Selenium was combined in one project in one test in order to close the technology. And we also see that coming from our customers. Okay, the next thing is, as I said, one of the most interesting things that we have over the last year. And it's how Linefstein and UFT are using web. Okay, so if you remember, I talked about Microsoft Edge and the fact that it came out of the box to support for web driver. And the thing is that in Edge they didn't have a, and we had to support that in our solution. So what we did is in Linefstein and UFT, we are actually web drivers to talk and to execute our UFT and Linefstein scripts directly on Microsoft Edge. So what happens is that we are actually using Selenium web driver C-Sharp binding. Okay, we are launching the Edge driver. We are talking to our own flavor of Microsoft Edge with the ability. Okay, so how it works? So we have on replay or record, if you like. So in the initialization phase, we are talking, we have the web driver host that is talking to either the browser driver or the mobile part with the app server. And then we are asking for a new web driver. Then we are getting the web driver session. We are sending the web driver execute script. It actually takes our agent and inject it into an adjacent that represents the browser that we are going to work with. And then some internal messaging. And from that point on, we are here. We are loading the web page saying UFT. Okay, we are ready to test. Okay, and what happens during the test? So let's say that we need to execute an action on an object. Then we send the query to the, we are executing the script and getting the object ID. So here this script contains the property of objects. And then once the object ID is returned, we are sending which method involved. We are executing the script, executing the method on the object. We get the response JSON. And then we continue working on the object. So for all. So this is how we use web driver to access a Microsoft Edge. And as I said, this was the first time that we use web driver in order to interact with any browser up till that point. We had our own agents, our own plugins. This was the first time that we use web driver to interact. Next part is mobile center, which is our one stop shop for mobile testing in the enterprise. We have a demo outside, make sure to come and see it. And it supports all sorts of functional testing, manual testing, sentiment analysis. Everything is being supported as part of the mobile center. And what we did inside mobile center, so we have a live demo working just outside. So make sure mobile app or device farm. So this, and this was the first time that we used open source 32 in an open in HPE code. First time, it was done last time. So everything that you can see over the last year, as I said, we changed the state of mind and are now using and leveraging and working together. And the last use case is the NFT that can be anything you can enhance the secure Selenium script, either with units other than web and mobile and also for improved object identification. So in case you have it, so the NFT was built from day one, either by having one project that uses both Selenium in the same script, both Selenium in the start with web driver, switch to the application model with the spy, and also we also have customers. I can also promise that this is only the beginning of the journey for us. And I can promise you that in Selenium conference in London, that was just announced yesterday, I will have much more solutions to tell you that we are currently working on. And also we are looking to give back to the Selenium community, whether it's several advanced locators that we are looking to contribute. We are also looking to contribute performance testing for Selenium and also some brand new solutions that just remember the robots. We'll talk about that. With that, be sure to come and visit us in our booth. I will take any questions if you have any. Cool. Thank you.