SeleniumUtil is an open source library to help make Selenium+Java automation easier and faster

I’ve been through two tech companies where they’ve had their own test automation frameworks. The last framework that I used was built to handle Web UI, API, and AS400. The framework was built by providing wrappers for common open-source automation components such as Selenium and Rest-assured. It was easy to set up an automation project using the framework, and only a few of us had any real concerns with it. It was the responsibility of the respective development teams to use the framework to automate their products based on a few loose programming guidelines. As the teams go through this exercise, they would build any custom components they might need as they see fit. Some of these components are universally used but were not available in the framework of the respective open-source components OOTB. Components such abstractions for working with HTML tables or custom ExpectedConditions. 

When I had some time on my hand I looked around to see if there are any open-source libraries that I can use out there to cut the automation project setup time and I found that there isn’t a lightweight library that can be easily integrated to existing projects. So I started one of my own.

At the moment the library provides a few wrappers for HTML elements such as RadioButton, MultiSelect, and Table. The plan is to implement other useful features such, Wrappers for common JavaScript script snippets, custom ExpectedConditions, and sliders. The library is at version 0.6.5 and it's available on Maven Central[1]. If you’re interested in contributing to the project please follow the instructions here [2][3].

[1] - https://search.maven.org/artifact/io.github.handakumbura/Seleniumutil/0.6.5/jar

[2] - https://docs.google.com/document/d/1Diudxs53eL8QkfYwHpExkusEtpJxF0mDHVrr6XymXYE/edit?usp=sharing

[3] - https://github.com/handakumbura/Seleniumuntil

 

 

How to create custom locator classes in Selenium and a few reasons why you should

Selenium supports many different HTML element locator strategies such as CSS, class, ID, and XPath. Xpath in my opinion is provides you with the most flexibility as it has features such as axes (build-in functions) and conditional operators. It would be hard to find an element you couldn’t capture in a sensible way with Xpath but it all depends on how good you’re with Xpath. So if you’re a test framework developer it makes sense for you to abstract out some of the common XPath templates into new By classes. Apart from reducing the chances of inexperienced test engineers making mistakes with the Xpaths, you can increase the readability of the code and provide means for greater reusability (through mechanisms such as ByChained).

Test Layer

Custom By Locator