Selenium HQ Reviews

We primarily use the solution for automating a solution on the web and automating testing.

We are a testing company. We can automate testing using Selenium.

The solution is very easy to use. Once you learn how to do things, it becomes very intuitive and simple. It's quite a user-friendly product.

The interface is great.

We've had good experiences dealing with support.

The pricing is fine.

Handling configurations is very good.

The stability has been good.

It's an easy product to set up and deploy.

If a company wants to scale it, it can. 

The product offers a free community edition. 

Selenium has problems with some objects. The objects are not in the squares of the screen. The layout can be a bit strange. It makes it hard to find objects.

We'd like to see some more image management in future releases. 

We've been using the solution for two years at this point. 

The stability is great. We haven't dealt with bugs or glitches. It doesn't crash or freeze. the performance is good.

If you need to expand the solution, you can. We've never had an issue with scalability.

We have about seven people using the solution at this time. 

Technical support is great. They are helpful and responsive. We haven't had a problem with them.

The initial setup is not complex or hard to do. It's pretty simple and straightforward. A company shouldn't have any problem implementing it. 

We have found the pricing to be reasonable. It's not too high of a cost.

We are actually using the community edition, which is free. 

We are a customer and an end-user. We don't have a business relationship with Selenium.

We have the solution deployed both on-premises and on the cloud. 

I'd rate the product at a nine out of ten. We've been very happy with the product. 

Currently I am doing mobile application automation with Appium and Selenium, as well as front-end application automation with tools like WAVE for mobile and desktop applications. The only area that I'm not involved in at present is API testing, though I am hoping there will be opportunities to get to that as well in the future.

We typically use Selenium and Appium in automation and testing by first identifying which modules we are able to automate. Then, whenever we encounter some new course in the framework that we're using, and we need to use a hybrid kind of framework, we will use Selenium to resolve it. 

Selenium has improved the way we work because if you do what we need to do manually, you'll have to expend a lot of time. For example, it would be a huge chore to navigate through an application manually every day, and particularly if there's a new build on the way, you would have to check all the regulations over again by hand. That would simply take too much time, and so what Selenium does for us is that in one resource it can handle the work of three, four resources, provided that the scripts are straightforward and coded properly. That's the main cool thing about Selenium, I would say.

For me, the most valuable feature of Selenium lies in its ability to help us find elements quickly. Apart from that, the driver interface is really useful, too. When we implement the Selenium driver interface, we can easily navigate through all of the pages and sections of an app, including performing things like clicking, putting through SendKeys, scrolling down, tagging, and all the other actions we need to test for in an application.

One drawback to Selenium is that there is nothing like an object repository, such as that found in QTP, especially considering continuous integration practices that have become common nowadays. In future, if they can provide an object repository or some kind of repository for data, then that I would greatly appreciate it. For example, once you have the app credentials and all the other security data and you don't want to show them to other people who are not authorized, a repository for this kind of data would be very useful. You could then simply grant access to only those people who need it.

Another improvement I can think of is in the area of documentation and support. With Selenium, we're using freeware software, and because of this there is no support or anything from the vendor. In this case, you have to rely solely on your own coding experience and exposure to the tool, and you often have to search through many pages of code when you want to change something in your implementation. It also makes you rely on your problem-solving skills to a large degree, because some problems are not that easy to solve by yourself.

If I can compare Selenium with another solution such as SoapUI Pro, there's a big difference when it comes to coding your own solutions. With SoapUI Pro, if you want to fetch some data, you don't need to write any code or anything, and for someone with no coding experience, this makes it much easier to be able to use effectively. So, ultimately, more support for non-technical people would make for a great improvement in Selenium.

I have been using Selenium HQ for the last two to three years.

The stability of Selenium depends on the skill level of the team that is using it. If you are writing solid code for automating your scripts, then you will find that Selenium itself is a stable solution. But if you're writing sloppy code then you may find that Selenium slows down or becomes unstable. Truly, I think it all depends on the people who are using it, and how they approach the architecture of the framework.

I am hopeful that Selenium will scale well because, along with others nowadays, we plan to to move into cloud-based provisioning with continuous integration. We will be doing that with AWS, most likely.

I haven't taken any technical support till now because Selenium is freeware, and you will not be getting any technical support directly. So that could be something that they could work on because if they were able to provide support, it would great for us and many others. Without it, you can still add code to the Selenium software itself, but they won't be able to help you with it.

On the other hand, I do believe there is enough documentation online for anyone who wants to figure it out by themselves. There are videos, tutorials, and other resources available to us.

The setup of Selenium is easy, in my experience, since it is provided as JAR files that you can download. Apart from that, there is, I believe, an architectural approach where you can simply input your dependencies and it will automatically download all the JAR files needed, and other required files.

As for deploying the code, this is just as easy. For example, if you're working with some type of continuous integration, it's a breeze to deploy. First, you have to build up your framework, and then you can deploy it to Git, or GitHub, or anywhere you want. At this point it's just about uploading the code, so there's not much to it. 

I am currently implementing Selenium along with a few other tools. For example, for mobile device automation, I'm using Selenium with Appium. The Selenium architecture can be integrated with Appium in order to be able to automate with mobile devices such as Android and iOS, which is what I'm doing now. Beyond that, we also have desktop applications; for Windows we have EXE files and for Mac we have DMG files. With these, I have implemented the Windows application drivers using Selenium so that we're able to easily automate any Windows-based or Mac-based app.

As for the rest of the team who are implementing Selenium this way, we have about 15 people on the testing side of things, and 6 people in automation.

Selenium is free software so we do not pay licensing costs. 

My advice to others is that, first of all, you have to understand the process of automation from a general point of view, and how people get on with the coding and all that. If you only have manual experience, like a lot of new testers, then you likely don't have much experience in coding either. And in that case, my advice would be to first understand the logic of the process. For instance, before jumping into it from the deep end, try get a handle on a few small steps first, and as you go along you will learn the basic coding, the basic architecture, how Selenium works, how the automation process works, and so on.

Then, take a piece of code and ensure that it works as a standalone script, then finally jump into the framework. Develop from any framework, use it as best as possible, get some experience with it, and try to become an expert from there.

You can use any programming language you prefer. As for myself, I'm using Java, but you can use C#, Python, Ruby, PHP, etc. There's a lot of support for different programming languages with Selenium. 

My biggest lessons while using Selenium have had to do with automation and how it really works, which is something I've always been interested in. Once I get an application, any application whether it be a WAVE app or mobile app, I very much enjoy getting stuck into the automation part of testing. And what I've learned is that not everything is that easy to automate.

In many cases, I have had to team up with new solutions and play around with code on my own, which has been a great learning experience for me. Apart from that, with Selenium I have been able to implement new things such as OCR (Optical Character Recognition) which is useful when you are not able to find all the elements you need, and I feel good that I was personally able to enhance the automation process with what I have learned along the way.

I would rate Selenium HQ an eight out of ten. 

The system is SaaS, and we use it for web-based regression tests that are being done locally at an in-home office or in the company office.

What I like about Selenium HQ is that we wrote it ourselves. I think it's perfect. It's a framework that you can use to devise your own products, which is nice.

Selenium HQ could have better interaction with SAP products.

I've been using Selenium for about a year now.

Selenium's stability is good.

Scalability has not been a problem for us.

We haven't really needed support. We write our own code, so if anything goes wrong, we can fix it.

Phil Ward:
Well, we set it up ourselves, so we knew what we were doing. Basically, the installation is ava-based, so you have to write Java code to get it working.

I would rate Selenium HQ nine out of 10. If someone is thinking about adopting Selenium HQ, I would encourage them to use it. However, you do need to be reasonably proficient in Java, C#, or C++.

We use Selenium HQ for automation and API integration.

The most valuable features of Selenium HQ are it is open-source, has a good interface, and integrates well.

I have been using Selenium HQ for approximately four years.

Selenium has been giving us failures sometimes. It is not working one hundred percent of the time when we are creating elements. They need to improve the stability of the solution.

The solution takes a lot of time for the developers. For example, if we are trying to implement UiPath or Automation Anywhere the people who are non-technical can use these two solutions. Selenium HQ is not easy for someone that is new to use, it takes too long for developers to learn the solution. There are other solutions that do not require such a learning curve.

We have approximately 870 users using this solution.

Selenium HQ has a large online community where you can get help on any issues or problems.

The installation is straightforward.

I have evaluated other solutions.

If you have developers that can operate Selenium HQ then this solution will be a good fit. However, if your developers are new to Selenium it might be better to choose another solution.

I rate Selenium HQ an eight out of ten.

Selenium HQ is used by our organization to automate test scripts for our applications as well as to automate or regression tests carried out during software development.

The grids, as well as the selectors, are the most valuable features.

The ease of use for the whole tool.

I would like more usability and ease of use.

The graphical interface could be improved. It would be very helpful to be able to write scripts in a GUI, rather than depend so heavily on the command line.

I have been using Selenium HQ in my department for three years.

Selenium HQ is a stable product.

It is easy to scale Selenium HQ.

We have five members in our Quality Assurance team, and three are dedicated to Selenium.

We have plans to increase our usage in Selenium but the issue is time.

We have not contacted technical support. In a Google search, you can find the help you need. It's an open community.

We worked with other solutions previously and changed to Selenium because of the cost of the license.

We are also using Microsoft Team Foundation (TFS), which is now known as Azure DevOps. We are upgrading to DevOps.

The initial setup is straightforward.

It took half a day to deploy.

One person is enough to maintain this solution.

We completed the installation and deployment internally.

The cost of the license is better than other solutions. Selenium is a free tool. It's open-source.

To date, we have not paid any additional fees.

I would recommend using Selenium with Python, it will be helpful.

I would rate Selenium HQ a seven out of ten.

I'm the company's managing director and we are customers of Selenium. 

 It enables us to handle some of the custom controls of Ajax calls to Selenium and Selenium Grid for parallel execution on different versions of the application and on different platform.

The Selenium stop control has been a challenge. We use auto IT for handling some of the small controls, small scenarios on the desktop, it needs to be improved with a configuration tool where it can handle desktop support as well as Ajax controls. Basically, there needs to be an improvement in handling the Ajax custom controls because the inbuilt method is not very helpful in that respect.

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

This is a stable and reliable solution for web applications, there is no doubt since it's an open-source tool, it's recommended for any web application. We used GitHub and Jenkins for continuous integration and everything is available online, we have experience working with the Jenkins version controls and configuration tools.

We use Google or blogs for any problems. There are sometimes delays and if we are moving into a new Chrome version or a new Firefox version, there can be delays of up to a couple of days to figure out the plugins and there's no immediate support available. We need to wait till something turns up on the internet. 

We've been using Selenium for a long time and haven't had many issues; we knew how to configure it. It's not completely straightforward and implementation takes time but everything was available on the internet and the blogs. There's a lot of documentation available regarding deployment. 

We're using the open source version. We don't have any support from Selenium HQ.

I would recommend this solution. If working on multiple browsers and on multiple platforms is the goal, then Selenium is definitely the right tool because it works on Windows as well as on Linux. It also supports multiple browsers. 

I rate the solution eight out of 10. 

My company started using Selenium HQ two years ago for unit testing. We were trying to evaluate the record and playback features. We are basically outsourcing this function, and we're charged for every developed feature and testing. So, we thought that we could test it ourselves using the record and playback feature. We were navigating our web application records in a macro and tried to reproduce that later. But for some reason, it's not the best solution for us.

I like the record and playback features. We also appreciate that it's not just writing on a script that we create. While we were browsing our web application, it automatically records all the clicks and movements of points. We also appreciate the fact that it provides screenshots of everything in the output.

It would be better if we could use it without having the technical skills to run the scripting test.

I think we have been using Selenium HQ for two years, but I only joined the company six months ago.

We are satisfied with its stability.

We are satisfied with its scalability. We have five or six users working with Selenium HQ.

Selenium is an open-source solution, and It's free.

On a scale from one to ten, I would give Selenium HQ a seven.

We are using selenium in our organization for Unit Testing, Smoke Testing, Sanity Testing and Regression Testing.

Reduces Manpower, Testing is become much faster which is helpful for faster Project delivery. 

Selenium supports a range of languages, including Java, Perl, Python, C#, Ruby, Groovy, JavaScript, and more. It has its own script, but it is not limited by that language. It can work with various languages – whatever the developers/testers are comfortable with.

Selenium provides support across multiple browsers, namely, Internet Explorer, Chrome, Firefox, Opera, and Safari. This becomes highly resourceful while executing tests and testing it across various browsers simultaneously.

I have been using this solution for approximately two years.

The stability of the solution has been good, it is reliable we have not had any bugs till now.

I have not connected their technical support. However, there is a lot of community support for Selenium HQ online. If you look on internet you can find plenty of solutions for challenges you are facing.

The initial setup is little complicated the installation could be simplified.

I would recommend this solution to others.