Using the Selenium open source project has so far been the only viable option for web development teams faced with the challenge of test automation. Selenium’s ability to drive browsers such as Chrome, Firefox and Internet Explorer using programming languages such as Java, C# and Python makes it possible for testers to work together with programmers — or alternatively learn programming themselves — to create test cases and the infrastructure to run them.

Unfortunately, even though Selenium is a powerful, free and open source tool, the time investment needed to learn how to program it and then setup an appropriate infrastructure for scheduling, recording and reporting is often counted in months. During the creation and maintenance of test cases, lots of methodologies from a programmer’s toolbox are required to achieve re-usability and not waste time “refactoring” code endlessly. And because test cases are written in code, working through them with product owners typically isn’t viable.

Additionally, Selenium only works on web browsers and cannot for instance be used on other applications such as Office and Windows apps, which means testing across applications becomes difficult. It’s clear that a different approach is needed. That’s what LEAPTEST is all about.

Easily find a LEGO toy on Amazon.com with image recognition using Leaptest instead of Selenium

The above is what a real-life test case looks like in LEAPTEST. It opens up the Chrome browser, types in “amazon.com” and hits ENTER, then clicks the search box on Amazon’s site, types in “lego”, clicks the category “Toys & Games” and checks that a certain LEGO toy can be found. This is very similar to what is being tested in the vast majority of Selenium cases out there.

Here’s what the same test case looks like in Selenium using the Microsoft C# programming language:

The difference is, it took a tester with no programming experience just a couple of minutes to put together the test case in LEAPTEST, but it took a skilled Selenium test automation programmer more than 45 minutes to do the same in Selenium because some complicated browser behavior had to be overcome and XPath statements crafted by hand.

For a live demonstration of how this exact case was created in LEAPTEST, please see ourĀ Tutorials for Getting Started.

Learn more about codeless test automation with Leaptest

TRY LEAPTEST FREE
LEARN MORE