I had a requirement to compare the images/screenshot of the application during the automation execution. In that use case, I have to inject an expected image and compare it against the application's UI during the runtime; after that need to share the test results in a detailed report. The report should capture the... Continue Reading →
No System.setProperty! No WebDriverManager!
In earlier days of web automation using Selenium, we used to start a driver session with help of many intermediate steps and third-party dependencies. We used System.setProperty to set the driver executable path prior to instantiating the session and used this method for many years as a traditional way to start the session,... Continue Reading →
Automated Page Load Time Tracker
I got an opportunity to work with a POC to capture web page load time tracking for an application. I have to map all the tracked time against the flow in an excel report. That excel report should have a benchmark time to compare the actual time. Finally, set the status based on... Continue Reading →
Start Appium Server 2.x using different languages
Appium Server is the core component of the Appium architecture. It is written in Node.js and runs on the local machine or in the cloud. Appium’s API is based on the W3C WebDriver Protocol, and it has supported this protocol for years. Before the W3C WebDriver Protocol was designed as a web standard, several... Continue Reading →
Pick the Right Locator Strategy during Mobile Automation
Here focus just on the selector strategies provided by Appium for native iOS and Android testing using the UiAutomator2 and XCUITest drivers. Here's prioritized list of locator strategies: accessibility id id XPath Class name Locators interpreted by the underlying automation frameworks, such as: -android uiautomator, -ios predicate string, -ios class chain -image 1. accessibility... Continue Reading →
journey of quality 