Step by step instructions to Make Selenium WebDriver Scripts Faster

The Selenium WebDriver contents are moderate since they gone through the program. There are numerous things that can enhance the Selenium WebDriver contents' speed such as quick selectors, less locators, nuclear tests etc.rnThe things that can enhance the Selenium WebDriver contents' speed are as follows:rnUtilize FAST SELECTORS:-rnSelenium WebDriver contents permit utilizing many sorts of locators. While choosing the locator, begin with the quick ones: rn1. look by ID rnThis works if the html component has the id property. It is the quickest locator as it utilizes the document.getElementById() javascript order which is streamlined for all programs. rn2. NAME selector rnThis works if the component has a name property. rn3. CSS selector rnIt is quicker than XPATH however not as adaptable. rn4. XPATH selector rnThis is the most adaptable methodology for building locators. In any case, xpath selectors are the slowest of all as the program dom of the site page should be crossed for finding the component. rnUtilize FEW LOCATORS IN SCRIPTS:-rnKeep the quantity of locators as low as conceivable particularly if utilizing XPATH. This runs together with keeping contents engaged and short. rnMake ATOMIC TESTS:-rnAbstain from testing excessively numerous things in a solitary content. It is smarter to have all the more little contents concentrated on one thing just than less huge contents that do an excessive number of things. • Each test should test a solitary minor piece of usefulness • Each test ought to have up to 20 stages. • Each test should keep running in less than 10 seconds. rnHaving nuclear test is extremely valuable if there should arise an occurrence of disappointments. The disappointments are clear about where the issue is. rnIllustration:-rnLet’s expect that one of the contents is called testSignupLoginChangePasswordLogout(). rnThis content checks 4 distinct things: • Information exchange frame works • Login works • Change secret word works • Logout works rnIn the event that the content falls flat, which part has a mistake? Information exchange? Login? ChangePassword? Logout? rnRather, we should utilize littler and nuclear contents: testSignup(), testLogin(), testChangePassword(), testLogout().rnIn the event that any of the littler tests falls flat, it is clear where the issue is. rnDONT TEST THE SAME FUNCTIONALITY TWICE:-rnEnsure that your contents are not looking at similar highlights and over. In the event that you watched that the login works effectively in one content, there is no advantage from checking it again in content. rnCompose GOOD TESTS:-rnGreat tests are made by following a couple of basic principles: • Great composed tests are quick tests. • Dispose of step duplication • Keep the contents free • Compose simply enough strides to go from A to B in the snappiest way that could be available • Evacuate steps that are not identified with the last outcome rnUtilize ONLY EXPLICIT WAITS:-rnA standout amongst other methods for making content quicker is by utilizing just unequivocal holds up. The content execution is better with express holds up as HTML components are gotten to when they end up noticeably accessible. No extra holding up times are required. rnUtilize THE CHROME DRIVER AND CHROME BROWSER:-rnOn the off chance that you require a genuine program, utilize Chrome and the Chrome driver. The Chrome program is quicker than IE, Firefox, Safari and Opera. The same is substantial for the Chrome web driver. rnUtilize HEADLESS BROWSERS AND DRIVERS:-rnOn the off chance that you don’t require a genuine program or you utilize constant combination, headless programs and drivers can make your contents quicker. A headless program is a program that does not have a UI. rnThe most mainstream headless programs are HTML UNIT and Phantom JS: rnHTML UNIT • headless program written in Java • uses the RHINO motor; this isn't extraordinary as this motor isn't utilized by any of the current genuine programs • provides javascript and ajax support and fractional rendering ability rnGhost JS • headless program that uses the WEBKIT format motor for rendering site pages and Javascript Core for executing scripted tests • the WEBKIT motor is utilized by genuine programs, for example, CHROME and SAFARI • uses Ghost Driver as an execution of the WebDriver Wire Protocol rnREUSE THE BROWSER INSTANCE:-rnA run of the mill JUNIT class incorporates the accompanying parts: • constructor • setUp() strategy • tearDown() strategy • test contents rnThe setUp() strategy utilizes the @Before comment and keeps running before each test content. Its motivation is more often than not to make the driver protest and open the program window. The tearDown() strategy utilizes the @After explanation and pursues each test content. Its motivation is to annihilate the driver protest and close the program window. rnEach test content is utilizing its own particular program case when the @Before and @After are utilized: rnTry not to LOAD ANY IMAGES IN THE WEBPAGE:-rnMany site pages are exceptionally rich in pictures so they don't stack quickly in the program. In the event that the page stacks quicker in the program, the content will be speedier too. The page will stack speedier if no pictures are stacked. This can be expert by setting up another profile for the program and impair stacking pictures for it.