Selenium HQ Reviews

We use it for test automation. We are also using Cypress for some of our automated tests. We've tried Selenium a little bit, but it depends on the project we are doing.

It is more stable in comparison to other solutions because they have quite some experience in the market.

I don't have that much experience with it, but I know that Selenium is more used for websites. It is not for testing desktop applications, which is a downside of it. It can support desktop applications more.

I have been using this solution for one year.

It is stable.

We have five people on the team, but not all of us are using it. We have plans to increase its usage.

It is not complex. I don't remember the time it took, but I do have development and testing experience. So, for me, it was an easy ramp-up.

I would recommend this solution to others. I would rate it a seven out of 10.

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 like that it is a robust and free open source. There is a lot of community support available, and there are a lot of developers using them. There's good community support.

In terms of improvement, there should be standardized frameworks, which do not exist. Currently, you have to first sit down and look inward. This function is provided by some tools like Katalon.

There should be standardized frameworks to build automation.

I have been using Selenium for five to six years. 

We also use Sauce Labs. We do testing on various versions of browsers, and various operating systems for Android and Apple. So Sauce Labs provided that capability, where we can easily scale up our testing to test on various versions.

The scalability and stability are quite good. It is easily scalable. With a few pieces of code, it's scalable.

We have interacted on the Selenium forums a couple of times but never contacted the technical support.

We also use Sauce Labs.

We set up the entire framework around how the tests would be and different class structures. Then we evaluated how to construct labs and how to title execution and stuff like that. It took us good four to five months of two or three people working on it, to set up a robust framework.

If you are using it for the automation test, automation is generally good. If you have an experienced developer, it will be really good to deploy the open-source frameworks for Selenium.

I would rate it a seven out of ten. 

Not a ten because they don't come loaded with the frameworks or different framework options. You have to build it from scratch. The build-in comes with a lot of networks and libraries and stuff. You still need to build that framework before you start writing the code

They try to come up with new features. I think they're in a very good space.

We took Selenium for web product test automation and as it very well suits as it has capacity to execute in different browser, different environment. Also it has lot other capacities to scale up test automation and yield better ROI.

Web-based application automation are mostly done using Selenium. It's the right automation tool as a replacement for manual regression testing that indispensably reduces the testing time due to its cross-browser, parallel, and remote executions.

- Most importantly, it is an open source tool.

- Parallel executions (same browser in parallel, different browser in parallel).

- Remote executions using Node and Hub.

- Integration with CI tools like Jenkins

- Multi-platform support (for details have a look at http://www.seleniumhq.org/about/platforms.jsp).

- Cross-browser Support (Chrome, Firefox, different versions of IE, Safari, Opera).

- Supported environments are Windows, Linux & Mac.

- Supports different scripting languages (JAVA, C#, Perl, PHP, Python, Ruby, Objective C, Javascript).

- Huge user community.

It has extensive support for Chrome and Firefox, but more is needed for IE, Edge and Safari.

To some extent it is unstable while executing against different versions of IE browser, but that could be overcome through some work-around and framework design. Edge browser executions are not stable as IE browsers.

Obviously, we have better support from various users as it is an open source tool. We have a huge number of customers in the open community at different levels to provide support.

Basically, to start with setup is straightforward and easier. If you use the remote web-driver, it is slightly complex to make the setup.

Our in-house team is used for the entire implementation of the framework. Being open-source, lot of valuable additions are made in a free-flow while developing the framework.

It's an open source tool.

• Videos of test cases
• Scalable multi threading test execution

We are now able to execute 3000 test cases in less than one hour. This is a great milestone for us.

It needs more support for mobile devices and also on testing web services.

I've used it for four years.Videos of test cases + Scalable multi threading test execution.

We've had no issues with deployment.

We've had no issues with stability.

We've had no issues with scalability.

It's open source and therefore there is no customer support.

We used a different product that was not open source. We wanted to use open source.

It was not too complex, however, it would be complex for someone who doesn't know much about automation.

I implemented it through an in-house team. My advice would be to foresee all the problems that you might run in to in the future and design the framework based on that.

Make sure you get the set-up right initially.

• Simple objects recognition
• It's easy to use
• Multi-language support
• Open source with good support
• A lot of information and help online

Selenium IDE needs to be improved not like just an record / play back tool, but as effective web elements spy. TestNG has more support, and also has ntegration with Appium and Jmeter which Selenium misses.

I've been using it for 10 years, since 2005.

Throughout the last five years, I have not had any difficulty to install or set-up Webdriver.

This is an open source, so some issues are always pop[ing up , but compared to other open source automation tools web driver is much much better.

It covers all regression testing with 20,000 test cases run during 24 hours and easy maintenance.

Customer support is very good for a non-commercial tool.

I used Silk Test and Win Runner previously. Borland SilkTest is an excellent tool, but it costs.

 It very straight forward and easy. Of course it’s required basic programming skills.

We have in house automation framework and it works great with continuous integration. I do not see reasons to pay for third party services.

It's a free tool.

Just use web driver and enjoy.

The ability to test on all of the major web browsers.

I’ve used Selenium in multiple ways of the years. In one case I was working on a web site that got updated once a week. Mostly by others. Every week we would find out that a page changed that we were not expecting because we had changed included content, not knowing it was appearing on another page. I convinced management to allow me to write a script that went to each page on the production site and compare the page to the stage site. I reported the changes to management so that if they didn’t know about them, they were aware of the change.

On another site, we used Selenium to do basic application level testing. Just about the time I would start to think I was wasting my time, the test would reveal a problem that needed to be addressed.

Can’t think of anything I would change.

I've used it for at least five years.

There's never been an issue with deploying it.

As the various browsers change, tests stop working. But that can hardly be blamed on Selenium. Every problem I've ever had has always been answered by “Get the most recent version of Selenium.”

I've never had a problem scaling the tests.

It is open source, I don’t think this applies. The documentation could use some work but there are books that fill this hole.

I had used TestComplete at one point a very long time ago. What I didn’t like about TC is that it was a complete development environment, which I didn’t really like. Selenium gives me the ability to write my test using the programming environment I am already familiar with.

The initial setup is pretty straightforward, but when you branch into using the Selenium Grid, things do get a bit more complex. It is all pretty easy now that I know how.

I implemented it myself using search engines and trial and error.

It’s free. And relatively easy to get setup.

Learn how to use the “Page Model” approach to creating tests. If you code direct to the Selenium API and don’t using the Page Model, as things change in your web application, it will become more and more difficult to update your test to reflect the changes.

It is compatible with and supports multiple languages, such as Java and Python. It is open source, and it is widely used.

It is not a licensed tool. The problem with that is that it won't be able to support Windows desktop applications. There is no support for Windows desktop applications. They can do something about it.

Its user interface can also be improved, which is not great compared to the other latest tools.

Anybody who has been working on functional testing or manual testing cannot directly work on Selenium HQ without learning programming skills, which is a disadvantage.

I have been using Selenium HQ for three years.

It has good stability.

Scalability is good. They are improving on that.

I haven't directly interacted with anyone. For most of the questions that I have, I search online, and I am able to find the answers in the community.

It is complex, but they have detailed documentation, which is helpful.

You need a person who knows one programming language thoroughly. It is not like anybody can pick and work on this solution. You should be thorough enough on the language and the framework that you are choosing. Only then Selenium HQ is the way to go.

I would rate Selenium HQ a seven out of ten.