Selenium-4-and-appium-2
•Download as PPTX, PDF•
0 likes•388 views
Presented this for the Ministry of Testing Bangalore Meetup group. This talk features some of new features of Selenium and Appium.
More Related Content
What's hot
What's hot (20)
Similar to Selenium-4-and-appium-2
Similar to Selenium-4-and-appium-2 (20)
More from Manoj Kumar Kumar
More from Manoj Kumar Kumar (11)
Recently uploaded
Recently uploaded (20)
Selenium-4-and-appium-2
- 1. A TA L E O F T W O T O O L S : S E L E N I U M 4 & A P P I U M 2 . 0 M A N O J K U M A R K U M A R @ M A N O J 9 7 8 8
- 2. A G E N D A • Selenium Architecture • Selenium 4 • WebDriver API • Relative Locators • Chrome DevTools Protocol • Selenium Grid • Appium 2.0
- 3. Test Selenium Server Grid/Cloud Browser/Driver Browser
- 5. SELENIUM 4.0
- 6. R E L AT I V E L O C AT O R S A friendly way of locating elements using terms that users normally use, • above • below • toLeftOf • toRightOf • near It started with Sahi. Sahi had Relation APIs, which are a lovely way of finding elements.
- 7. H O W D O E S R E L AT I V E L O C AT O R S W O R K ? • Every element on the DOM has clientBoundingRect – Relative Locators are based on it. • Measured from the center-point of the client bounding Rect https://developer.mozilla.org/en-US/docs/Web/API/Element/getBoundingClientRect
- 9. C H R O M E D E V T O O L S • The Chrome DevTools Protocol is developed to enable a debugger inside Chromium-based browsers. Selenium 4 now have native support for Chrome DevTools Protocol through “DevTools” interface. • This helps us getting Chrome Development properties such as Application Cache, Fetch, Network, Performance, Profiler, Resource Timing, Security and Target CDP domains etc.
- 10. A U T H E N T I C A T I O N • Selenium 4, offers a mechanism to register a username and password that can be used to authenticate against these sites.
- 11. N E T W O R K I N T E R C E P T I O N Selenium 4 allows you to stub out the backend of the application, intercepting network traffic in the test and returning pre-canned responses
- 12. S E L E N I U M G R I D
- 13. G R I D M O D E S • Standalone • Hub & Node • Distributed • Docker
- 14. Router New Session? New Session Queuer Event Bus Distributor Session Map Yes No New Session Queue Node Requested Capabilities Node Client Error No Selenium 4 Grid Flow
- 15. G R A P H Q L Q U E R Y I N G S U P P O R T F O R G R I D 4 • What You Ask Is What You Get. • GraphQL is an API specification standard and an Open-Source data query and manipulation language. • It has a server-side runtime fulfilling those queries along with the data.
- 16. G R I D O B S E R V A B I L I T Y • Selenium server is instrumented with tracing using Open Telemetry. • Every request to the server is traced from start to end. • Each trace consists of a series of spans as a request is executed within the server. https://github.com/manoj9788/tracing-selenium-grid
- 17. V I S U A L I Z AT I O N O F J A E G E R T R A C E S
- 18. W E B D R I V E R B I D I
- 19. APPIUM 2.0
- 20. A P P I U M 2 . 0 V I S I O N Decouple the drivers: The code for these drivers will no longer be bundled with the main Appium server Enable Driver Ecosystem Decoupling helps users to look at existing Appium drivers as a template, anyone can create their own custom drivers with a minimum of extra code Enable Plugin Ecosystem Plugins let you add arbitrary functionality before or after Appium commands. Also modify server.
- 21. A P P I U M 2 . 0 • Provide support for any app platform beyond Android and iOS • Will expose common driver classes and functionality • Make it easy for anyone write and share Appium drivers • New drivers can be easily shared in different means like Git, Npm etc… • New Drivers • Roku (Smart TV app automation) • KaiOS (feature phone app automation) • ChromeOS/Chromebook
- 22. A P P I U M 2 . 0 I N S TA L L AT I O N
- 23. A P P I U M 2 . 0 • By default, Appium creates a hidden directory called .appium inside your user home directory. But if you'd like to use a different directory, or if you want to keep multiple driver repositories around, you can adjust this path by using one of these three command line options (which are all aliases of the same behavior) • For example, appium -ah /path/to/custom/appium/home driver install xcuitest.
- 24. R E F E R E N C E S • https://www.oreilly.com/library/view/distributed- systems- observability/9781492033431/ch04.html • https://github.com/manoj9788/tracing- selenium-grid • https://www.jaegertracing.io/docs/1.17/getting- started/ • https://www.headspin.io/blog/appium/first-look- at-appium-2-0-and-new-drivers/
- 25. T H A N K Y O U Manoj Kumar @manoj9788
Editor's Notes
- You know, finding elements on a page can be really difficult. I've seen loads of people using very complicated XPATH expressions, and trying to figure out complex CSS selectors and things like that. There have been whole talks about the subject at SeleniumConf. Surely there must be a better way to do this? Think about how we describe where an element is on the page. Think about how you’d do this over the phone. You’d never talk about the raw DOM, “Ah, find the fifth DIV element nested inside the SPAN with an ‘id’ of ‘foo.’” You’d just never say that! Instead, think off a conversational way of telling elements where they are in the page - you’d say something like, “just find that thing above that image, and to the right of that link,” when talking about where things are located on the page.
- You know, finding elements on a page can be really difficult. I've seen loads of people using very complicated XPATH expressions, and trying to figure out complex CSS selectors and things like that. There have been whole talks about the subject at SeleniumConf. Surely there must be a better way to do this? Think about how we describe where an element is on the page. Think about how you’d do this over the phone. You’d never talk about the raw DOM, “Ah, find the fifth DIV element nested inside the SPAN with an ‘id’ of ‘foo.’” You’d just never say that! Instead, think off a conversational way of telling elements where they are in the page - you’d say something like, “just find that thing above that image, and to the right of that link,” when talking about where things are located on the page.
- It started with Sahi. Sahi had Relation APIs, which are a lovely way of finding elements.
- Right hand side of 1 is left of the left most edge of 2 The top edge of 2 is at the same level as the bottom-edge of 1 This means that 1 is above 2 and 2 is below 1
- One feature that people have been asking for since we started the project has been the ability to authenticate to a web site. Previously, you could do this by crafting the URL the browser went to properly, but this leaks credentials to any man-in-the-middle and leaves them in server logs, so browsers have slowly removed this piece of functionality. That’s unfortunate, since it’s something that we know people frequently need to do in their tests. In Selenium 4, we now offer a mechanism to register a username and password that can be used to authenticate against these sites.
- A common complaint of Selenium tests is that they’re slow and flaky. While the bindings to the browser are excellent, and fully described by the W3C WebDriver spec, it is true that any end-to-end test is likely to suffer more flakiness than a simple unit test—there are just more moving parts, and more possibilities for things to go wrong. One way to resolve this issue is to stub out the backend of the application, intercepting network traffic in the test and returning pre-canned responses. Tools such as mountebank make this easy for API testing. Wouldn’t it be nice if there was a similar tool for Selenium? With Selenium 4, we now provide a mechanism to do this, using the NetworkInterceptor (well, that’s what we call it in the Java bindings). Pass it your WebDriver instance, and it’ll be called every time the browser is about to make an HTTP request, allowing you to return almost anything you want.
- Router faces the internet and take incoming traffic and figures out....where to send it.. If the request belongs to an existing session, the Router will send the session id to the Session Map, and the Session Map will return the Node where the session is running. After this, the Router will forward the request to the Node. If it is a new session request, the Router will forward it to the New Session Queuer, which will add it to the New Session Queue. Upon successfully adding the request to the queue, The New Session Queuer will trigger an event through the Event Bus. . The Distributor picks up this event and polls the queue. It now attempts to create a session If the requested capabilities do not exist in any of the registered Nodes, then the request is rejected immediately and the client receives a response. If the requested capabilities match the capabilities of any of Node slots, Distributor attempts to get the available slot. If all the slots are busy, the Distributor will ask the queuer to add the request to the front of the queue. The Distributor receives the request again after the request retry interval. It will attempt retries until the request is successful or has timed out. If request times out while retrying or adding to the front of the queue its rejected. After getting an available slot and session creation, the Distributor passes the new session response to the New Session Queuer via the Event Bus. The New Session Queuer will respond to the client when it receives the event.
- WebDriver BiDi The original WebDriver spec is designed to allow you to have the test running very remotely from the browser. So SauceLabs, BrowserStack services like that are easy to do, but also you can set up like an internal grid at work. Things like Puppeteer, Cypress, Playwright, things like that. They assume that you're running locally and what they do is they hook into the browser debugging protocols. And the main difference between the browser debugging protocols and the WebDriver spec, there are many. The major one is that the browser can send events to your test, right? So when people say, oh my well, my test using Puppeteer is so much faster. What's actually happening is an event is coming from the browser. And they're saving 200 milliseconds, 100 milliseconds. Instead of polling for an update, they get the update coming straight to them. Now, the problem with depending on a browser debugging protocol is obviously these things are designed for debugging browsers And so they change with every single release of the browser because there's no requirement for them to be stable API that people write code against. You want to be able to take the same APIs and apply them consistently between browsers. And so what we're doing with WebDriver BiDi is we are taking the lessons learned from that event-driven model where the browser can send events and you can send commands to the browser in a sort of bi-directional way. So you can find an element using the current W3C WebDriver spec. And you can pass the element into WebDriver BiDi. And similarly, you could take a reference from WebDriver BiDi and you could use that in standard W3C WebDriver.
- The Webdriver protocol, as you can tell in the name, was originally designed for automating web browsers. And, you know, it’s already the case that Appium uses this same protocol to automate mobile applications. We simply extended it in a few ways and added some additional capabilities, but by and large, if you look at an Appium test script, it looks and reads very similar to a Selenium test script.
- Appium's platform drivers (the XCUITest driver, UiAutomator2 driver, Espresso driver, etc...) have very little in common with one another. This decreases the size of an Appium install dramatically, and makes it so that you don't need to install drivers that you don't need to use. Plugins: So what are plugins? Plugins basically let you add arbitrary functionality before and/or after Appium Commands. So if you think about the findElement command you could write a plug-in that when the findElement command comes into Appium, instead of sending that command on to the typical driver, you do something else with it. Some good examples of this would be the Find Element by Image API or the Appium + Test AI Classifier.
- Npm install –g Appium@next Do Appium to show the list of errros Appium driver list Appium driver install uiautomator2
- https://github.com/appium/appium-plugins/tree/master/packages -ah to specify a directory to install Appium drivers appium server -ah /path/to/install/drivers driver install uiautomator2copy code to clipboard -ka or –keep-alive-timeout to specify the number of seconds the Appium server should apply as both the keep-alive timeout and the connection timeout for all requests. Defaults to 600 seconds. appium server -ka 800