In the early 2000s, a test engineer named Jason Huggins came up with an idea. It was an idea that would make his job, as well as many other testers’, a whole lot easier. He created a software tool for web browsers and applications that enabled him to automate his testing, making it possible to find out if the code he wrote worked across all web browsers.
Fast forward to almost 20 years later, and a lot has happened.
A few more bright-minded test engineers pitched in with their additions to the tool, resulting in countless testers around the world taking it up and implementing it as a core part of their testing.
Today, Selenium is a popular software testing tool that is open-sourced and supports most browsers and operating systems. It’s perhaps most popularly known for allowing testers to automate in any preferred programming language.
The problem is this: Not all testers know how to program (we call this the Selenium Paradox).
For this reason, testers can end up spending a significant amount of time on setting up and maintaining automation flows – more than they save once the automation is set up. So, the question is: Is Selenium worth the time investment?
To help you answer this question, we have put together this whitepaper.
In this whitepaper, you will get:
- An overview of the Selenium tool suite
- The pros and cons of the tool as a whole
- A guide to evaluating if Selenium meets your testing needs
- An alternative to Selenium that solves many of the problems faced by Selenium users
