Selenium HQ Reviews

We use the solution to perform tests and robotic process automation.

The solution helps us improve and maintain a specific set of work quality. Also, it saves a lot of time for us.

The solution's core functionality is excellent.

They should add more functionality to the solution. Also, they should provide technical support services.

We have been using the solution for five years.

I rate the solution's stability a ten.

It is a scalable solution. I rate its scalability a ten. It is easy to deploy on any device.

I used Micro Focus UFT One earlier.

The solution's initial setup takes time. I rate the process as one. We require a specialist to download and install it manually. Later, we need to create a framework and set it for an automation process. The entire process is quite complicated for new users.

The solution is an open-source tool.

I recommend the solution to others. Its learning curve is very high for Java and comparatively less for Python. Apart from this, it is highly stable. A lot of documentation is available for it in case of any queries. I rate the solution a nine.

We are using Selenium for web test automation.

We are saving time with regression testing by using test automation.  

Selenium is also open source, so now we are integrating all our automation tests into the full pipeline. 

Selenium is very famous. Due to its popularity, you can find pretty much any answer in open discussions from the community. This is the power of Selenium. Whatever you need, whatever your question, you will find an answer.

The initial setup is easy.

You can integrate the solution with pretty much anything.

It's open-source and free to use.

Maybe they could improve the record and play plugin for element detection. That would be ideal. If they could build some tools above Selenium for that, I'd find it helpful. People sometimes do not have that much technical knowledge, and having something more plug-and-play would be appealing.

We have many plans in our pipeline that still need to be implemented. Maybe we will find that we need some features that need to be integrated with Selenium, for example, for a multi-browser or for implementing many machines. We haven't fully implemented this solution yet.

The drawback is the solution is not easy to learn. You need resources and technical knowledge and have to deal with the maintenance of script changes. 

While it works well with Chrome, if you use it with other browsers, you may have issues. 

I've been using the solution for three or four years. 

We've never had any stability issues. It's reliable. The performance is good. It doesn't crash or freeze.

It is scalable. It's easy to expand. 

We have about 15 people working on the solution. 

I've never spoken to technical support per se. We tend to get help via the community if we have questions. It is quite robust and there is a lot of information about all kinds of issues publicly available. 

I have used other tools as well. Each tool has its own pros and cons. Each organization also has its own unique needs. There are budgets, resources, and other factors that would come into play as well.

The solution isn't difficult to set up. It's quite straightforward. 

I'd rate the ease of setup eight out of ten. 

I cannot recall exactly how long the deployment itself took. 

Sometimes there may be some maintenance required around upgrades. You would need to check the compatibility between the software, for example. That said, the maintenance requirements are pretty low. It's not complex to maintain the product. 

We handled the implementation ourselves, in-house. 

This is an open-source solution, which is a very positive benefit. 

I'd rate the solution six out of ten. It's not an out-of-the-box solution like Oracle or SAP. 

We primarily use the solution for normal regression tests.

I like most of it. It is possible to get a lot of help and find help on the internet since Selenium is so widespread and established. The documentation is great.  There is  a lot of help on websites like Stack Overflow.

It is very stable.

The product is open-source. 

We are thinking about codeless automation, like what ACCELQ offers. They could maybe release a similar product that would be a codeless product.

The initial setup was difficult. 

It would be nice to have it on the cloud, like ACCELQ. That way, we don't need to set up it ourselves and don't need hardware for that. That would also allow for many people at many subsidiaries or locations to work simultaneously with it.

I'd like the possibility of automatically checking the installed browser version and automatically downloading the Selenium driver that suits the installed browser. Otherwise, you have to download and set up it manually, and if you get a new browser version, you have to do it every time, and it's time-consuming.

We've been using the solution for one year. 

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. 

Of course, you need a lot of time to optimize your scripts so that they run stable.

This is not really scalable. 

If you consider load tests or multi-thread testing, you need very powerful hardware to start several browsers. That's why in this aspect, not very scalable if you run tests in parallel.

We just have two people leveraging the solution right now. They use it regularly, on a daily basis. 

There is a lot of documentation and general product knowledge online. We don't have direct support contact as it is an open-source solution. 

We did previously use Eggplant. It's not open-source. It's actually pretty expensive. 

One benefit of Eggplant was testing mobile apps. Also, you don't find so much information on Stack Overflow or on the internet about Eggplant; they have good support.

It was not very easy to set up. 

We needed to add a lot of plugins like TestNG and Maven. The whole configuration was not very easy. I am not sure if it is the Selenium setup or just the whole system setup.

The solution is open-source and free to use. 

I'm an end-user. 

The solution is okay, however, you need to use it together with the TestNG and with Maven and use different plugins that improve it.

I'd rate the solution nine out of ten.

SeleniumHQ is WebDriver-related. It is a package that we can use with any language such as Java or Python.

We use Selenium for automation purposes. For example, if we need data from a website, we write code that will extract the data automatically. If there are logins or pop-ups, the code will close them, so we can extract the data. 

When we are testing a website, we use SeleniumHQ automation testing to determine if there are any bugs.  

The most valuable feature of Selenium is how easy it is to automate. For example, often when data is needed, someone will sit and copy and paste it. What we can do with SeleniumHQ is automate it so that the data is directly extracted from the tools and libraries that we use. This saves time and is much better than copying and pasting.

There are some tiny issues with SeleniumHQ. For example, with respect to the scraping tests. Sometimes, a website will have some hidden items or blockages that inhibit us from extracting data directly. It would be beneficial if Selenium could extract that information.

The other issue is browser-related. There are small bugs causing it to break automatically. Sometimes it will close automatically. 

I have been using SeleniumHQ for a year and a half.

Stability depends on how you write the code. If you handle all conditions, there will be some surprises. Suddenly, you will have pop-ups and other conditions. 

SeleniumHQ is scalable. Anyone can use it. We have approximately 30 users of the solution. 

Customer service and support with Selenium are good. If any bugs are found and brought to their attention, they will immediately help. They provide lots of documentation as well as answers on the internet. The technical support team, themselves, will answer questions within 24 hours.

We use Python, so the initial setup of SeleniumHQ was quick and simple. You can use any browser or tools like, Chrome, Firefox, or Edge to run the automation testing. 

We are using Selenium open-source, so there is no need to purchase anything.

We evaluated other options. 

For mobile scraping, non-mobile scraping, or to test anything mobile there are more applications available on the internet, like Appium for Android, which is like Selenium for browsers, or TestComplete for iOS drivers. 

However, Selenium is particularly the best for browsers or PC, operating systems.

I would recommend this solution to anyone considering implementing it into their organization. Overall, I would rate SeleniumHQ an eight out of ten.

We mainly use HQ for UI automation and some of the main functions of test cases. We are customers of Selenium. 

The best thing about the product is that it is open-source and free, which is why we opted for it. It's also customizable which is great for us. There is a lot of online assistance available in forums and support on the Stack overflow. HQ is continually updated and supported by Selenium. You can write your own scripts without needing to depend on what's already there. The UI is automation friendly. When there's a slow network and an older application, the waves get very flaky and Selenium can handle that. Setting up and working with Chrome and Firefox is easy on Selenium.

The solution is intended for browser automation so it's not a support testing tool and there are no features. I'd like to see some flavors of test case management available that don't require any additions and there could be some improvement in the fluid-based area as well. Selenium is meant for developers but QA people cannot write test cases very easily on it. If you don't have a development background, it's tough. 

I've been using this solution for eight years. 

We had a few stability issues initially but it's very stable now.

The product is scalable. We have around 40 to 50 QA users in the company. 

We reported a few bugs on Selenium and they were resolved. The support was mediocre. Because it's open source there's not much support available.

The initial setup is easy but it requires certain development skills to set up. Without that, it's not easy. The difficulty is in creating a framework and that requires thinking about the maintainability and scalability aspects.

We went with Selenium for several reasons; it's open source and free, they provide a lot of support, and we can use Java technology which Selenium has available. Other tools generally don't provide perpetual licenses.

It's important to get hands-on experience with the program. I would also suggest getting your frame pyramid in order. You need to decide on the language you're going to use and have that programming language support in your organization and decide which other tools you're going to use. Also, think of your application and whether Selenium is the appropriate solution.  

This is the most widely used tool throughout the world in this space. It has so much support available and is a benchmark for other tools so I rate the solution eight out of 10.

the primary use cases of this solution are UI regression testing and API automation testing.

The most valuable features of this solution are its flexibility, being open source, and it has close to no limits when it comes to integrating with any language, or browser you are using.

The solution can be improved by providing better reporting logs.

I have been using the solution for four years.

This solution is the most stable product I have used when it comes to web automation.

This solution has no scalability limits.

The initial setup is easy, like a walk in the park for any user.

I implemented the solution in-house.

The solution is open source.

Before choosing the solution I evaluated Cypress and Postman. 

I give this solution nine out of ten.

When it comes to UI testing this solution is perfect but for API automation it lags behind compared to Postman.

Around 70 percent of our engineers use this solution on a daily basis.

Since the solution is open source you can create a user account on GitHub and receive free community-based technical support when it is required.

The solution is for front-end testing. It is mainly a testing tool.

There is nothing I cannot do with Selenium. It's very good in terms of features.

The recent changes they've added have been positive. 

The back-end integration and backend web driver supports are great. We integrate with Jira Confluence, Bitbucket, and Jenkins. There is no issue at all.

It has great Dev tools.

The Chrome debugging protocol has been helpful.

We found the initial setup to be straightforward. 

The solution is stable.

It's quite scalable. 

This is an open-source solution that is free to use. 

It supports multiple languages. Many of my friends are working with Selenium with Python language. I am working in Java. People are working in Javascript also. Some people work in this Ruby, C#, et cetera. 

In my previous company, I was using Selenium in my MacBook Air. They could handle iOS with no problem or Windows. It supports different operating systems and multiple browsers. 

It's really not lacking in features at this time. 

We'd like to have more support for Windows applications. 

There's no in-built reporting available. They should work on their reporting functionality. 

I've used the solution for five and a half years. 

It's a pretty stable product. There are no bugs or glitches. It doesn't crash or freeze. 

It is scalable. I have made many changes, and it is always scalable. It is adaptive, actually. Whatever I do on it, I can adjust. It is scalable.

We have maybe ten people using the solution right now.

We use it daily. 

Whenever we Google issues, we find it easy to find answers. 

We've found support to be good.

I've also used Appium in the past.

The solution offers a very easy initial setup. It's not overly complicated or difficult. Compared to Appium, for example, it's much easier. 

I'd rate the ease of implementation five out of five. 

The product is free to use and open-source. 

The framework and the language should be defined early if a new user plans to take this solution on long-term. It helps to have that figured out so you can implement it correctly. A few years back, I started with Java, however, given the choice, I would have preferred Python.

I'd rate the solution ten out of ten. 

We use it when you have a large number of scenarios to be tested manually, you would go for a web-based automation solution.

It is a good automation tool.

I would like to see Selenium HQ support legacy platforms.

I have been using Selenium HQ for the past five years.

I find Selenium HQ to be a stable product.

Selenium HQ is scalable for our needs.

Selenium HQ is not complex to work with.

We deployed in-house and it took between two to three weeks to complete.

The licensing pricing depends on the customer's needs.

It is a straightforward application to learn. If you know Java, it is something that can be easily learned and used. It has a lot of support out there. But again, it might not support some of the older back-end platforms. I would rate Selenium HQ an eight out of ten.

I'm currently working on automation testing using Selenium and Cucumber. 

I am using it with Java, not with as a standalone implementation. It's Selenium with Cucumber and with TestNG.

It's a dependency that I am using from SeleniumHQ. It's a couple of components.

We primarily use it for automation testing. 

The standard features are good, and I use them a lot. The framework for testing is robust with Selenium.

The integration with TestNG and Gherkin with Cucumber is great. Gherkin is a language for using for testing.

The solution is stable.

You can scale the product.

There is a supportive community around it. 

It would be awesome if there was a standalone implementation of Selenium for non-developer users. For example, for business users. If a business wants to test something and doesn't have the knowledge of coding and programming, they should still be able to.

They should offer a single setup. By that, I mean software that you don't need to set up component by component. They should make up a setup file that puts all software together in the place that it should be and it works.

I've been using the solution for six months. 

Selenium is a mature and stable software. There are no bugs or glitches. It doesn't crash or freeze.

Selenium is not so scalable. It's not like other software. There are a couple of dependencies where you can make it grow or shrink depending on your needs. In general, it's okay.

I haven't used support a lot. I have researched a couple of posts in the community. I've done no more than that.

The initial setup was not quite so complex and also not simple. I tried it in Eclipse, and it didn't work quite well, and then I tried it in IntelliJ. I need to look further into it if either can be used with Selenium. I didn't use it with Eclipse. I used it with IntelliJ. With IntelliJ, the implementation was pretty straightforward, pretty simple. However, with Eclipse, it's not.

We are customers. 

I'd advise users to take advantage of community posts. If the person finds any trouble, Google it. Probably someone already has found the same issue and also has found the solution or the workaround for it.

In general, I have no complaints about this product. I would rate it nine out of ten.

The bank uses Selenium HQ for web application automation. We write functions in Java with the TestNG framework. Working with a reusable library, we develop classes for the login, homepage, and remaining components. Once you create everything for the web application, we run scripts in Jenkins overnight, and then come back to our framework if there are issues. Finally, we use Eclipse to debug the code.

Selenium HQ lets you create your customized functions with whatever language you want to use, like Python, Java, .NET, etc. You can integrate with Selenium and write. 

You can also connect to a database using your JVC to read and write the data. This is the best feature. You can create your functions here, so it's scalable in that sense. You can make any custom function. You need to write the code.

Selenium HQ doesn't support Windows-based applications, so we need to integrate with the third-party vendor. It would be great if Selenium could include Windows-based automation. You need to integrate it with a third-party tool if you want to upload any files. When we interact with a Windows application, we usually use Tosca.

It also doesn't support dynamic capture, graphical presentation, or cloud functionality. We need to integrate with multiple things.

I've been using Selenium HQ for four or five years. 

Support team? No. We actually made a request ... actually, there is no such support, but we extended the Selenium, whatever, we have it, we extended in our COE team, center of excellence. So wherever we are facing the issue, we just contact them. So they try to resolve our issue.

The initial setup is effortless. We only need to download Selenium HQ from the Oracle site and follow some steps, then it's installed. You install the correct version for Java and configure Selenium. It's complex compared to Tosca, but if you have some knowledge on the programming side, you can easily do it.

The time needed for deployment depends on the code, the complexity of the application, and the number of restrictions you have. Deployment takes around 30 minutes to an hour.

There is no license. It's open-source and there are no additional costs.

The bank chose Selenium HQ because it's open-source. It's scalable and we can extend it as needed. That's why we decided to use it.

I rate Selenium six out of 10. If you want to use Selenium, you need basic programming skills in Java, .NET, or Python as well as knowledge of the TestNG framework. You should know how to identify the object from the application and use the developer tool.