Selenium Automation/Manual Test

Selenium Page Object Generator Chrome Extension This chrome extension helps in creating the page object class for Selenium WebDriver with locators for all available elements and methods to access them. It uses a template to generate the class which can be customized from the settings page of the extension. Selenium Page Object Generator is a good tool to improve the workflow. It will generate Page Object Model on active Chrome tab with a single click, provided that all the options and template are configured. The generated Page Object Model can be saved to pre-configured Chrome download folder. It currently supports 3 different targets: Java, C#, and Robot Framework. You can search for this extension in Chrome Browser. PageObjectGenerator Extension Once we add this extension to Chrome, we can easily generate Page Objects for the applications which we need to automate. Usage: Launch Chrome browser and the extension can be found at the top rig...

Run Selenium Tests In Headless Google Chrome Selenium is one of the most popular, open source and efficient browser automation tools available today. With Selenium Web Driver, it automates several (browser) actions, such as opening a webpage, clicking a link, checking the URL, and so on. But there are cases when you may need to run automation tests in ‘headless’ mode, i.e., when no browser is being displayed. In these cases, you can execute Selenium tests in headless browsers. This is useful when testing in cloud Dockers/linux What Is A Headless Browser? A headless browser is a simulation module/browser which do not have user interface. These programs operate like any other browser, but do not display any UI. When Selenium tests are run, it executes in the background Benefits Of Headless Browser Testing: 1. Improves speed and performance Since this type of testing does not actually open a browser, the system saves the processing power that would otherwise be used...

How to inspect disappearing element in a browser: In selenium scripting we should  use right techniques for identifying the web elements. In few cases when there is disappearing items like KendoUI, we should use smart ways/techniques for identifying the elements rather than spending lot of time behind analyzing the javascript/reactjs codes. Technique/Tools  1.  For finding the elements and xpaths, we can use the tools like  ChroPath, CSS Selector or any other Chrome plugins 2. Once we identified the proper xpath or elements with id/css, we can confirm its presence with similar tools like Xpath Helper Wizard Then, we can use it in our page factory logic So, challenge here is, few elements like KendoUI date pickers closes soon after changing the focus,  To find elements of these kind we can use 2 techniques: 1. In Chrome,  Open devTools (F12) Select the "Sources" tab While the element you want is displayed, press F8...

Evolution of Selenium - Part 1 Selenium Webdriver Selenium Record and playback IDE Selenium GRID Why Selenium: 1. Its open-source and highly matured tool for web testing 2. Open source tool 3. Selenium have huge user base with wider support 4. User can choose different binding languages depends on need 5. As it is language independent, it robust and easy to access Database or APIs for deep verification Different Types of Selenium : S elenium Webdriver  If you are beginning with desktop website or mobile website test automation, then you sghould use WebDriver APIs. WebDriver uses browser automation APIs provided by browser vendors to control browser and run tests. This is as if a real user is operating the browser. Since WebDriver does not require its API to be compiled with application code, it is not intrusive. Hence, you are testing the same application which you push live. Selenium IDE IDE (Integrated Development Environment)...

Bandwidth throttling  is the intentional slowing of Internet service by an Internet service provider. It is a reactive measure employed in communication networks in an apparent attempt to regulate network traffic and minimize  bandwidth  congestion. Now a days releasing the client-server application to the market without testing it in all  possible network speeds such as Edge/2G/3G/4G/LTE various Wi-fi speeds, tethering etc is very dangerous. This is highly risk prone areas for the client-server apps. Normally the companies would be having high speed internet/4G  connections and the QA Team forgets about the normal end user cases such as  network  disturbances, low bandwidth, repeated disconnection etc... Then what would be the solution for this? How the QA should identify this in early stage? The solution found by moderntester is Bandwidth  throttling  using proxy tools! Charles can be used to adjust the bandwidth...