We just raised a $30M Series A: Read our story

Selenium HQ OverviewUNIXBusinessApplication

Selenium HQ is the #3 ranked solution in our list of top Functional Testing Tools. It is most often compared to Eggplant Digital Automation Intelligence: Selenium HQ vs Eggplant Digital Automation Intelligence

What is Selenium HQ?

Selenium HQ is a suite of tools to automate web browsers across many platforms. Selenium runs in many browsers and operating systems and can be controlled by many programming languages and testing frameworks. Selenium consist of two types:

  1. Selenium WebDriver - create robust, browser-based regression automation suites & tests and scale & distribute scripts across many environments.
  2. Selenium IDE - create quick bug reproduction scripts and create scripts to aid in automation-aided exploratory testing.

Selenium HQ is also known as SeleniumHQ.

Selenium HQ Buyer's Guide

Download the Selenium HQ Buyer's Guide including reviews and more. Updated: September 2021

Selenium HQ Customers

BrowserStack, Sauce Labs, experitest, Tricentis GmbH, SmartBear Software

Pricing Advice

What users are saying about Selenium HQ pricing:
  • "It is all free."
  • "Selenium is open-source."

Selenium HQ Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Michael Fadhl
QA Automation Engineer at XPO Logistics
Real User
Top 20
Highly customizable and the best tool out there to do automated testing

Pros and Cons

  • "Its biggest advantage is that it is very customizable."
  • "We use X path for our selectors, and sometimes, it is difficult to create locators for elements. It is very time-consuming because they're embedded deeply. A lot of that comes from the way that you architect your page. If devs are putting the IDs on their elements, it is great, and it allows you to get those elements super fast, but that's not necessarily the case. So, Selenium should be able to get your elements a lot quicker. Currently, it is time-consuming to get your selectors, locate your locators, and get to the elements."

What is our primary use case?

We basically use Selenium for smoke testing and regression testing. We don't use it much for functional testing because you can easily and manually use a bunch of tests and make them a Zephyr. We use Zephyr as our test case management tool, which is a kind of a plugin for JIRA. So, we create our test cases in Zephyr, and then they are tagged to be automated. After that, we put them into our regression suite. Each team has its own independent regression suite. Currently, my team has a couple hundred, but I know some teams have 500 or 600 in their suite. We also have a suite of smoke tests that we run through Selenium.

All the code is on-prem. We're currently just running the tests through the Jenkins pipeline, but we want to be able to run them in parallel in the cloud and a lot quicker. We are not quite there yet. 

How has it helped my organization?

When we execute our smoke test, we're able to perform them really quickly with Selenium. Currently, in our project, we have 12 smoke tests. If I have to run them sequentially, it is going to take half an hour. If I run them in parallel, each one of them takes less than two and a half minutes. So, I could do smoke tests in under three minutes and get feedback right away about whether everything is up and running. We do production deployments throughout the week, but we try to do our main deployments on Sunday. Sunday is not the best working day, but because it is a weekend, we can get our work done. We want to be able to perform these tests quickly. The same is applicable to our pre-prod environment. We can run our smoke test right away, and it will be able to tell us that all the dependencies for our applications are up and running. As compared to doing it manually, which can take a few hours, it is really quick. 

It saves time for regression testing. It takes about three people to do the regression testing manually for probably two or three hours, whereas you can do it a lot quicker if you can get them in parallel. So, you can get quick feedback about whether your application is up and running right away. You don't want to go down the road where you find a problem after four or five hours. You want to find it out as quickly as possible.

What is most valuable?

Its biggest advantage is that it is very customizable.

It saves time and enables us to execute our smoke test and regression tests really quickly.

What needs improvement?

We have a lot of inheritance going here. I've been doing it for so long, so it is pretty straightforward for me, but you have to know Java to be able to work in our framework. I know some people use Python, but you have to know Java. That's kind of the hardest thing when you're doing interviews. People just don't know Java. This is where probably Worksoft has an advantage because it is codeless. So basically, you are just pointing, clicking, and providing things like Excel spreadsheets for your test data. In that sense, if you are using Worksoft, it is a lot easier to train or onboard somebody.

We use X path for our selectors, and sometimes, it is difficult to create locators for elements. It is very time-consuming because they're embedded deeply. A lot of that comes from the way that you architect your page. If devs are putting the IDs on their elements, it is great, and it allows you to get those elements super fast, but that's not necessarily the case. So, Selenium should be able to get your elements a lot quicker. Currently, it is time-consuming to get your selectors, locate your locators, and get to the elements. You have to find the element on the page, and then you have to go to the page and the console. In the console, you can put the next path in there to locate the element manually in the JavaScript to say that this one will work, and let's use this because we'll put a string of that element. After that, we get the element based on that stream. That's probably the most time-consuming part of that. It is dependent on how well you've designed the front-end UI. We use something called Data Tests attribute through which we can locate elements super fast. If people consistently use those, that's great, but a lot of times when they go in there to fix some bugs, they're not consistent in doing that. They usually just find a way to locate the element and change that in the code. If you change something, then your code or your test is going to fail because the locator has changed the element, and you can't get it anymore. You have to manage a way to get it. So, when you're running your suite of tests and you see some failures, it takes some research to find out why did this paneling go, and then you find out that it happened because of the frontend change. Someone removed this element and changed it, and you have to change your locator, which is very time-consuming. It is kind of like a false belt. It is failing, but it is not. It is only failing because of your locator. It is not failing because the app is not functioning correctly. It is a kind of false failure. Sorting the elements quicker would be a big thing with Selenium.

For how long have I used the solution?

I have been using this solution for eight years.

What do I think about the scalability of the solution?

We have a dozen teams at our company, and each one of them is independent. We give them a pretty extensive Selenium framework, and then they basically start building based on that architecture and create their test cases and page objects.

In terms of its usage, Selenium is our testing framework. We use Jenkins to perform our test cases. A lot of them are done through a pipeline, and a lot of them are queued on to run automatically. There are triggers in there to run something every day at 9:00 AM. We don't have to manually say that we want to test this aspect of our page. 

The excellence team now has four people, and that's just the team that manages the framework. There are 25 people who can do test automation. They do manual tests and automation. They use the same framework, and if they find some issues, they'll ask us. If they're constantly having to do a certain function and having to write the Selenium code for it, they will ask us to do that. We might create a tool inside the framework to make their life quicker. We can put it inside the common Selenium framework so that it is always available to everybody.

How are customer service and technical support?

Selenium is an open-source solution. If you have a problem, you can pretty much Google something and figure out a solution for it. There are so many people who are using it, and there is a lot of material that is available out there for you to troubleshoot any kind of problems.

You don't usually directly go to the open-source code. I don't visit it at all nowadays. In the beginning, I did do it a lot, but not so much now. We're now in a state where we are just executing test cases and creating new ones. It does everything we need and meets our needs.

Which solution did I use previously and why did I switch?

It has been Selenium for me from the get-go. I've been here at XPO for almost five years. Before that, I was more of a contractor, and I did a couple of contracts. When I went to a healthcare company, they really didn't have a great framework. So, I started one, but I doubt that they're still using it. That's because it requires a lot of knowledge to be able to create a framework.

It is something that I've been always using. I've done some research on some other tools to be able to do things, but I always come back to Selenium. 

We're an angular-based house, and all our pages are in angular. There are some other products that run on top of JavaScript besides Selenium. There are quite a few people out there who are using Protractor, which is an end-to-end type of test framework, but it works specifically for angular applications. We have never gone down that path. We just stuck with Selenium.

How was the initial setup?

When I first came here, the framework was in place, but it was more basic. There is a team of three guys here, and we're all pretty smart. We're the excellence team for the framework. We've done a lot to make it a lot simpler for us to create our test cases. Three people probably worked 25% of the time for a few years on it. So, a lot of time was invested into the framework, and it has come a long way. It is much more sophisticated now.

Maintaining the architecture and Selenium framework for testing requires work. It is an ongoing kind of process. We're constantly maintaining it and updating it.

What's my experience with pricing, setup cost, and licensing?

It is all free.

What other advice do I have?

Each product has its own pros and cons. It is very customizable, but then you have to have a lot of knowledge about Java or an object-oriented programming language that works with it. They keep creating frameworks to make your life easier, and it is a very customizable framework, but you have to have the knowledge to be able to do it. There are other tools out there, such as Worksoft, for which you don't have to know Java.

If you're starting from scratch, it would be good to get a good Java developer and make him or her get everybody up and going. That Java developer can train junior test automation people. You should hold on to that person for as long as you can. Getting a good Java person is probably critical when you're creating your Selenium framework.

It is not the easiest thing because it is hard to get a quality assurance resource that is knowledgeable about Java. So, it is very difficult to get a good framework in place. Usually what happens is that you'll get QA people who start doing QA, and then they start doing test automation. Once their skills get up there in Java where they're decent, they move over to being a software developer. So, they get out of the QA world, and they go over to be a developer. So, you lose that talent. You had to do your framework, and now they're gone. Maintaining good talent is difficult. It is hard enough to maintain the Selenium framework, and when you start losing people, it makes it harder. The next person comes in line, and it is just a revolving door. 

I would rate Selenium HQ an eight out of 10 because it is not perfect, but it is the best tool out there to do automated testing.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
SG
Director Technology at Simplify 3x
Consultant
Gives a lot of freedom to code anything, there is no restriction on the type of function you can do

Pros and Cons

  • "What I like the most about this product is that it gives us a lot of freedom to code anything, there is no restriction on the type of function you can do."
  • "Selenium is good when the team is really technical because Selenium does less built-in methods. If it came with more built-in and pre-built methods it would be even easier for less technical people to work with it. That's where I think the improvement can be."

What is our primary use case?

We work for a client who does HRM solutions. They wanted us to develop their scripts using Selenium HQ. Typically, we develop UI, API and database scripts. These are the three combinations we have used for them. So their test cases are typically where we initially do some operations on the various applications they have. Then, once the operation is done, we initiate a few API calls and then we validate the data in the database. This whole process of trying to enter into, listen into, and close is done using Selenium HQ. This is what we are doing. We have close to 8,000 test cases in the last three years.

What is most valuable?

What I like the most about this product is that it gives us a lot of freedom to code anything, there is no restriction on the type of function you can do. Typically, we use Java with it, and Java has a lot of libraries available online, and whatever you need you can just write the Java code for that part of the work and then you can do it. This includes, multi-technology, the UI database, API image based testing - it lets us do everything.

What needs improvement?

Selenium is good when the team is really technical because Selenium does less built-in methods. If it came with more built-in and pre-built methods it would be even easier for less technical people to work with it. That's where I think the improvement can be.

I would also like to see a good method for image based automation. That's what I believe is a very upcoming thing and is something that Selenium really lacks. The imagery is kind of an automation. It's more of an object decipher, so that's something I really want to see because most of the tools are moving in that direction.

For how long have I used the solution?

I have been using Selenium HQ for three years.

What do I think about the stability of the solution?

It is stable, but one issue I see is that whenever there's a new version coming in, every three months or so, the current version changes and the new version of Selenium is not stable and then we have to wait for a week or so to get a patch for that.

We use Selenium HQ on a regular basis.

Overall there are around 20 people working on this just in my area, who are also responsible for delivery as well as maintenance.

What do I think about the scalability of the solution?

On a similar previous project, we scaled it. We went ahead and integrated the continuous integration and Jenkins Pipeline with QA. It was pretty scalable. We were able to connect it to CID and we were able to connect it to JIRA.

How are customer service and technical support?

In terms of customer support, it is more of a community support. There's a lot of small communities for Selenium HQ. I don't think Selenium HQ has official support. But there are a lot of communities. So typically we go to Stack Overflow and that kind of community where we just look for the support if we get stuck.

How was the initial setup?

The initial setup was pretty easy. There is lot of online documentation and online help. Even if you get stuck somewhere it just takes a few searches to figure out the issue because there is good community support.

What about the implementation team?

We were able to deploy and install this product all by ourselves without any extra help.

Which other solutions did I evaluate?

We tried MicroFocus UFT and we also evaluated Tosca. These are the two tools we evaluated along with HQ but we felt Selenium HQ was better for us.

The overall need for this project was that we were supposed to integrate across multiple technologies. When we started this project two years back we had to use API and a UI database. We were not allowed to use a lot of technologies. So we realized it would not be easy with other tools to combine three technologies in the same place since it's a different structure. This was not possible with UFT or Tosca. So that was one of the biggest reasons we chose Selenium HQ, because the whole project depended on that kind of a flow.

Additionally, there was the licensing issue. It was pretty costly at Tosca and MicroFocus UFT, whereas Selenium HQ is all open source and has a very good community support. So I think these are the two reasons we chose it.

What other advice do I have?

My personal advice is that it is such an amazing tool to work on. The best thing about the tool is the community support. I don't think any other tool has that kind of a community support. You just post a question on any popular community, like Stack Overflow, and you get answers in like 20 minutes. There are so many people using it which makes life really easy. At the same time, you get a lot of free hands to work on. Meaning because it's based on Java which has so many open source libraries, you can use any library to do any kind of functionality you want. That's a pretty powerful tool. My advice if you get stuck somewhere, is to just put it on community and then you get your answer.

On a scale of one to ten I would rate Selenium HQ an eight.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Learn what your peers think about Selenium HQ. Get advice and tips from experienced pros sharing their opinions. Updated: September 2021.
540,884 professionals have used our research since 2012.
KR
Software engineer at a financial services firm with 10,001+ employees
Real User
Open-source solution is faster than most but lacks some features

Pros and Cons

  • "Selenium is the fastest tool compared to other competitors. It can run on any language, like Java, Python, C++, and .NET. So we can test any application on Selenium, whether it's mobile or desktop."
  • "For now, I guess Selenium could add some other features like object communications for easy expansion."

What is our primary use case?

Depending upon the functionality, I use Selenium to prepare the scenarios I'm doing. I start by writing automation scripts in Java. From there, we execute the scripts if there are any changes in the product. Then we upgrade this overnight along with Jenkins to make sure our application is running as expected. They feature continuous deployment and continuous integration with the help of our teams, so our product will be applied to more users once it's adequately tested.

What is most valuable?

Selenium is the fastest tool compared to other competitors. It can run on any language, like Java, Python, C++, and .NET. So we can test any application on Selenium, whether it's mobile or desktop. And if I build some framework on Selenium, I can give it to someone else. Then they can use it and start going further. One more thing is that you can implement any framework on it, like TestNG, Cucumber, JUnit, etc.

What needs improvement?

Selenium should implement more islands for a desktop feature. My laptop and desktop have a calibrator or some other desktop applications. We can automate those things through Selenium, so they should be adding them in the subsequent versions. For now, I guess Selenium could add some other features like object communications for easy expansion. 

For how long have I used the solution?

I've been using Selenium HQ for about five years.

What do I think about the stability of the solution?

So performance-wise, Selenium is the best tool so far. It has the fastest automating tools.

What do I think about the scalability of the solution?

We run scenarios at midnight or around that time and split this application into virtual machines. So during that time, the application is executed in panel mode. Let's say I have 10 vital missions in the Google Cloud Platform. These things will be triggered automatically and executed in each of the machines. And it has a balancing load concept, so if one machine is at capacity, it will automatically move to a second machine for the other scenarios. So there is never an issue with scalability. We have more than 1,000 employees in the company using it every day to develop scripts. 

How are customer service and support?

Because Selenium HQ is open source, we don't have a customer service team or technical support, so we have to search on our own for answers. When I've had problems in the past,I've had to Google to see if it's an application issue or a Selenium issue. Without any help from vendors, it's difficult to automate some things like CAPTCHA. But still, we have a framework that is ready for this. So with the help of this framework and importing those library files, we can make our own way. 

Which solution did I use previously and why did I switch?

At my previous company, we used a UFT tool called Micro Focus UFT. We used this because it was a different kind of use case where we had to transfer our publications back and forth between the mainframe and the mobile application. So we have to format that, which is why we used the UFT.

How was the initial setup?

Setting up SeleniumHQ isn't that complex. We like to develop our application in Pega and have a point cloud that we deploy on Google Cloud. It is developed and tested with Jenkins, which is a continuous integration tool. Once the code is specific to Jenkins, we trigger Selenium and execute the scenarios. After this finishes, we move everything to cloud. 

Along with this docker, there is a deployment phase in Google Cloud, where the images of our application are moved to pre-production. Pre-production is something like a replica of production that allows the users to work on it. So once it is transferred to pre-production, the users will work for one week or one or two. If they are satisfied, we move on to production.

Deployment usually requires about eight to ten people. Most of the work is done by technicians who are akin to database administrators. They take this on for one month a year every year. Their job is mostly to minimize the weight of the application. In the next phase, DevOps engineers deploy the enviornment. The time for deployment depends on the teams and the tasks. If there is a small change, it may have taken between half an hour and an hour. On the other hand, if there is a significant upgrade of the application, it may take eight to ten hours. Generally, we don't need any maintenance unless a UR application has changed.

What's my experience with pricing, setup cost, and licensing?

Selenium is free. Anyone can use it without paying anything.

What other advice do I have?

I rate SeleniumHQ seven out of 10. When you're choosing a solution, it depends upon the type of applications you are using in your project. If you have only have desktop and mobile, go for Selenium. However, if you have multiple applications like Windows-based applications, a virtual machine-based application, or a mainframe .NET application, I suggest going with another tool, like Tosca UFT.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Google
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
reviewer1652511
Lead QA Engineer at a tech services company with 501-1,000 employees
Real User
Top 10
Open source, easy to install, detailed documentation, and easy to integrate

Pros and Cons

  • "Data parametrization and parallelization are the most important features in any automation tool."
  • "I continuously see failures in threads when it is running in parallel."

What is our primary use case?

We are still testing Selenium HQ.

The client is based in the U.S. They process the code checking, and we work on the script.

When we get storage or requirements for manual testing, we begin the automation once it is stabilized.

How has it helped my organization?

We work in the healthcare domain.

If for example, I get a diagnosis for a particular patient, it continuously changes as there are at least 100 sets of data. It's impossible to make that work for each and every build manually. The parameterization and parallelization have helped us with the inputting. 

Every week we have reviews. We have automated the stabilized areas. It has helped us to add speed to our cycles.

What is most valuable?

Data parametrization and parallelization are the most important features in any automation tool.

Speed is very important for continuous integrations and deployments. The team gets more time to focus on other new areas.

The configuration of different data sets is also very important.

With Selenium, it is an open-line, I can integrate at any time, from anywhere.

What needs improvement?

There are some network issues, as the line is not very clear.

There are some areas that need improvement. I continuously see failures in threads when it  is running in parallel. 

I find that it fails, especially when I use APM automation on the mobile side. I have experienced these issues, and since the APM is also based on the Selenium pack.

It is a challenge to locate them, or knowing the location of the unique elements on the APM application. I don't see many issues with the Web applications but there are several with the APM.

As an open-source solution, there is no dedicated support.

Extending functions on the codes would be very helpful.

For how long have I used the solution?

I have been working with Selenium WebDriver for four to five years but in the last year, it has been working mostly on the functional testing.

What do I think about the stability of the solution?

There are some issues with the stability of Selenium HQ.

What do I think about the scalability of the solution?

In terms of scalability, we don't use many distributed systems. It is for a limited number of users. We have one lead architect and three senior QAs.

How are customer service and technical support?

We don't deal with technical support. Our clients handle that on their end, but there is no direct technical support.

Which solution did I use previously and why did I switch?

I have some experience with Selenium WebDriver and Rest Assured API automation. 

In regards to mobile automation, we use Appium.

Six months ago, I work on Selenium NUnit.

How was the initial setup?

Clear instructions were provided to complete the installation. It was very straightforward. There were no issues when installing this solution.

APM setups are a bit more of a challenge. It takes longer to set up APM.

There were no issues in the installation of WebDriver. From the end-to-end process to deployment, to the automation code.

What about the implementation team?

We have one dedicated assigned person for continuous integration and deployment. We check in with him before we complete any code. We provide him with our test and script, and the integration is done with him present to avoid any issues.

What's my experience with pricing, setup cost, and licensing?

Selenium is open-source. There are no licensing fees with Selenium.

Which other solutions did I evaluate?

We are currently evaluating functional testing tools, both manual and automation testing.

We are looking for codeless automation with support for codeless automation.

In my evaluations, I have seen that some are tools are lacking.

What other advice do I have?

I have worked full-fledged on Selenium WebDriver along with the multi-tenancy for the JavaScript framework.

I have hands-on experience with the Selenium framework, and I also worked on, API for APA automation Currently I am working in the healthcare domain.

In my opinion, it is a complete end-to-end solution.

As of now, it's for only web APIs. It provides a complete solution. 

I don't see that it's many disadvantages, except when doing the coding. A person should have perfect coding skill sets. If they don't have a coding skillset, it's a little difficult for them to get started. 

We had completed multiple POCs to present to our clients.

It was pretty straightforward for me. I didn't experience a lot of difficulties getting into Selenium. If your framework with Selenium is good, then it gives you the correct output.

I would rate Selenium an eight out of ten.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Harold Rios
Director at Finding
Real User
Top 5Leaderboard
Free to use and available on different platforms but has a complex setup

Pros and Cons

  • "The solution is free to use."
  • "For people that don't know about technology, maybe it's difficult to use."

What is our primary use case?

In my company, I use the tool for testing web browsers.

We basically use the product for two things. The first is for testing for a website. The other thing is for repeating actions so that you can repeat the same action over and over with ease and without having to repeat the original steps. 

What is most valuable?

The solution is free to use. It's open-source, and you can modify the source. 

You can use it on different platforms, including Windows, Linux, or macOS.

It's easy to find and receive help from other developers. There is a good community that surrounds it.

The solution has been very stable so far.

What needs improvement?

Sometimes it's difficult to understand the solution. It's a good solution, however, it has many specific things you need to know, or you need to learn about. For people that don't know about technology, maybe it's difficult to use. You have to know how to program. You need to be a developer.

The tool has two steps: first, when you record, and second when you play back. However, in the middle, you need to look at a file. You need to save a file and after that look at them. It would be ideal if the solution allowed for the process to be one step and more automatic. 

The initial setup is quite complex.

For how long have I used the solution?

I've been using the solution for maybe two years or so at this point. It's been a while.

What do I think about the stability of the solution?

The stability of the solution is good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

What do I think about the scalability of the solution?

I've never tried to scale the solution, however, it's my understanding that it is possible. On a scale from one to ten, I'd rate the potential to scale at a six or seven.

The tool is open source. Typically, when something is a commercial solution, there is more of a possibility of being scalable. We depend on other developers to grow the tool. 

Last year, we only had two people on the tool. However, this year, I want to grow that number to about ten. They are all engineers. Of the team, 80% would be quality engineers and 20% would be developers.

How are customer service and technical support?

I don't use Selenium technical support. As an open-source tool, you need to go to the community and the forums.

Typically, you can find your answers pretty quickly. You can ask the community as well, and usually, someone gets back to you pretty fast.

Which solution did I use previously and why did I switch?

I also use SmartBear. Selenium only works for web browsers, and sometimes I need to check an application. When that is the case, I cannot use Selenium, and I instead use SmartBear.

How was the initial setup?

The initial setup is not straightforward. It's pretty complex.

It's complex due to the fact that you need to download a complement for the web browser and you need to recall the tests and you have to load the files. When you do a recall, the tools create a file with the steps. Before you need to playback, you need to load the file. It's not easy. You need to know some things about the tool. 

The deployment took maybe six months to possibly 10 months.

You only need one person for deployment and maintenance.

What's my experience with pricing, setup cost, and licensing?

The solution is open-source and free to use. There are no licensing costs.

Which other solutions did I evaluate?

We did look at Katalon Studio before ultimately choosing Selenium HQ.

The principle difference is Katalon is one solution. You can't change the functionalities in the solution. It's also complex to use and demands a lot of memory. You need a lot of RAM or a big processor. It just takes up too many resources. 

What other advice do I have?

We are just a customer and end-user.

I'm not sure which version number we're using. However, it is a version from 2020, from the last year or so.

I'd advise those considering the solution, if you want use SeleniumHQ, it's a good option if you have good developers that understand the tool and can make changes in the tool. If you have the right people on hand, it works very, very well.

I'd rate the solution at a seven out of ten. If it didn't need such technical expertise, I might rate it higher.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
NC
Software quality engineer at a healthcare company with 10,001+ employees
Real User
Saves a lot of testing time but needs better integration with third party tools

Pros and Cons

  • "My customer previously validated every file and it would take almost 15-20 minutes for a document. They used to randomly select and test only 100 out of the thousands, maybe 85,000, files, to pick up sampling. Each file would take around 20 to 25 minutes, so we were not able to do it manually, but with the help of Selenium, we were able to test all the files in two days. It saves a lot of time."
  • "Sometimes we face challenges with Selenium HQ. There are third party tools that we use, for example for reading the images, that are not easy to plug in. The third party add-ons are difficult to get good configuration and do not have good support. I would like to see better integration with other products."

How has it helped my organization?

My customer previously validated every file and it would take almost 15-20 minutes for a document. They used to randomly select and test only 100 out of the thousands, maybe 85,000, files, to pick up sampling. Each file would take around 20 to 25 minutes, so we were not able to do it manually, but with the help of Selenium, we were able to test all the files in two days. It saves a lot of time.

What is most valuable?

Selenium HQ is open source, which is one thing that I like about it. Whatever you want to find, it's already there. If you'd like to add some features, you can. You can also contribute to it. Whatever problems we face, we can go and add. It is most like Eggplant, which is a paid tool, but here we don't have to pay for anything.

What needs improvement?

In terms of what could be improved, there are some glitches with it, but whenever you report it, the open source community works on it and fixes it. There is no support here. If I say in the user community that it's not working, I have to go and check Openstack and extract questions and answers from the community. There is not any company that is supporting it that could help me. There is no particular documentation about it that can help me in a technical way. I would have to see people's user experience and see what they have done in such and such scenarios.

Sometimes we face challenges with Selenium HQ. There are third party tools that we use, for example for reading the images. They are not easy to plug in. The third party add-ons are difficult to get good configuration and do not have good support. I would like to see better integration with other products.

In the next release, I would like OCR, image recognition, to be built-in. Sometimes there are no code elements that are detectable so finding x paths is tough. Whenever there are some challenges here, we could use OCR or something similar, with good image recognition.

For how long have I used the solution?

I have been using Selenium HQ for the last couple of months.

What do I think about the scalability of the solution?

Selenium HQ's scalability depends on the modularity of the product. Our product was more modular. When we made the product testable for one document, we were able to test 20,000 documents with it. So the scalability was quite impressive.

We have three people in the testing team who are using it.

We are considering expanding usage. Since it has reduced the business time, there are new scenarios that other business teams were using it for. So they asked us to include those scenarios as well, reducing the time.

How are customer service and technical support?

There is no tech support because it's open source in Selenium.

You just have to raise the bugs in the community and if someone has time, they can fix it. So it's not so quick.

How was the initial setup?

The initial setup was straight forward. We don't use it in deployment, we just use Selenium for testing in our organization. The code which was deployed was tested before.

There are four developers in my team who are working on it.

It was not a Selenium deployment because the deployment was of code, and we only use Selenium for testing purposes. We did not deploy with Selenium code anywhere on production.

What's my experience with pricing, setup cost, and licensing?

In terms of pricing, it is open source, so we don't have to pay anything for Selenium.

What other advice do I have?

My advice to anyone considering using Selenium is that using their libraries is good but the focus should be on finding the elements. Element location is a tough part. There are plugins that are available so don't waste time creating your own locators. You can use ready-made built-in solutions that would reduce your time a lot.

On a scale of one to ten, I would give Selenium HQ a six.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Sunil Pandey
Assistant QA Manager at a tech services company with 51-200 employees
Real User
Top 20
Purely API so integration is possible with any tool; web scraping is a key feature

Pros and Cons

  • "Ability to integrate with every other tool."
  • "Could have additional readability and abstraction."

What is our primary use case?

Our company is a customer of Selenium and I work in QA.

What is most valuable?

One of the most valuable features of this solution is Web Scraping although overall I think every single feature of Selenium is valuable because it's purely API so we can integrate it with any other tool.

What needs improvement?

In terms of improvement, I think there could be additional readability and abstraction in the solution, similar to the way other frameworks function. The solution could possibly use a more generic framework with more machine learning. If the community or IT companies had the budget, they might be able to work on that but it would definitely improve the solution, particularly in areas such as image comparison and image recognition. Machine learning capability would enable a self-healing capability in terms of locators. Selenium is not a magician, you need to provide instructions in order for it to identify any element in the web. That would really be an advantageous feature. Jason Arbon, CEO at test.ai, demonstrated this in Appium, which derives from Selenium. 

I'd also like to see a one-click install package. For now, I have to use TestNG, then Java, and then build them back. That could be simplified. 

For how long have I used the solution?

I've been using this solution for almost five years. 

What do I think about the stability of the solution?

It's a pretty stable solution but we have to be careful and make sure we're using what has been released. We need to know which version to use and make sure it's the latest one so we know it will be stable. 

What do I think about the scalability of the solution?

We are a small setup so have four or five users in the company. I've worked in bigger companies where thousands have used the solution on a daily basis, so it's very scalable. 
It's not the solution that deals with scalability, it's the cloud or a virtual system that enables scaling. If there are 1,000 test cases that I want to commute in an hour, then sometimes the reports can be messy.

How are customer service and technical support?

We use Selenium forums most of the time and we get most of our answers from there. There are multiple people online providing answers. Selenium does provide a service but we don't use it because we are self-sufficient in that respect.

Which solution did I use previously and why did I switch?

I have used Coded UI from Microsoft, which I believe will be deprecated some time this year. That was a very good solution. Before that, I also used HP QTP. Both of those are easier solutions than Selenium but also quite expensive. 

How was the initial setup?

The very first setup several years ago was quite complex, nowadays it is simple. Generally we use Maven, so it is simply importing and doing the setup. If I already know the settings, it can be deployed within half an hour. It depends on the system configuration so there can be issues sometimes. Setup can easily be done internally and if there are good community people there could be a one-stop solution layer where installation is one click. Maintenance is only required when there are updates or API changes. 

What other advice do I have?

The solution requires good understanding of Python, Pearl or Java and it's important to use the documentation. It would take a few hours of watching video sessions or reading the documentation to get started. It also helps to have an understanding of how API works, the architecture and how Selenium interacts with browsers. Having the background helps to design something with more features. 

I would rate this solution an eight out of 10.  

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PRADEEP PAMIDIPALLI
Project Lead at a computer software company with 1,001-5,000 employees
Real User
Top 10
Has good remote server features and an easy implementation

Pros and Cons

  • "The solution is very easy to implement."
  • "The login could be improved, to obviate the need for relying on another one for integration with Selenium HQ"

What is our primary use case?

We employ the version of the solution with the most ease of use, based on a search we conducted five or six years back. We now have a new client who likes the approach we used with a different one. We have a script to download the latest version, integrate it with the regression suite and then run it. Our current and previous clients equally approve of this approach. We make certain to utilize the latest version even when conducting tests during the development stage, as we find it easy to work with.

What is most valuable?

Remote server execution is a feature we find most valuable. We make use of Selenium Grid as concerns parallel execution. We also find the ordinary features of Selenium Grid to be valuable, 90 percent of our purchases comprising UI and 10 percent back-end.

What needs improvement?

In the past, we had difficulty with screenshots, but this has been remedied. We feel that all the current solutions are usable and the providers are helpful.

This said, the login could be improved, to obviate the need for relying on another one for integration with Selenium HQ. It would be nice if the solution provided an internal login system, one which would allow us to easily debug it. Until such time as a login system will be added from the vendor application, it will not be possible to identify the exact cause of a potential failure, unless there should be an interaction with, say, the UI element. Selenium HQ currently allows for an exception should an element be stale, not be found, or intractable. 

For how long have I used the solution?

We have been using Selenium HQ since 2007.

What do I think about the stability of the solution?

The solution is very stable. I always suggest Selenium, even when conducting internal training. As I consider this to be a better solution than that offered by the competition and one which works, I do the same with my team. I always advocate on behalf of the ease of integration of Selenium HQ.

How are customer service and technical support?

We have not made use of Selenium HQ’s technical support. We belong to a forum site that we joined some time ago while looking for help in finding an integration solution on the pipeline side. We were able to obtain all the information we needed from the Selenium HQ forum. Meaning, there was no need to contact anyone else with our frequent questions.

How was the initial setup?

The initial setup of the deployment cycle and the process of onboarding users takes an average of 10-15 minutes. This is the length of time it takes for us to set up in our pipeline the data repositories for the regression suite, and, subsequently, integrate the data with Selenium HQ, which is the point at which we run it.

What other advice do I have?

We implement the solution for our clients, not simply resell it.

The solution is very easy to implement. The first step which must be done is to go through the documentation on the site. I feel the solution to be pretty straightforward and people are drawn to it by its ease of use. There is always help available on the web for integration or implementation issues.

I rate Selenium HQ as an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
Buyer's Guide
Download our free Selenium HQ Report and get advice and tips from experienced pros sharing their opinions.