Selenium HQ Reviews

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 are using Selenium HQ for automated UI testing of web applications.

The most valuable features of Selenium HQ are the automation of all UI tests, its open-source, reliability, and is supported by Google.

Selenium HQ can improve by creating an enterprise version where it can provide the infrastructure for running the tests. Currently, we need to run the test in our infrastructure because it's a free tool. If Google can start an enterprise subscription and they can provide us with the infrastructure, such as Google Cloud infrastructure where we can configure it, and we can run the test there, it would be highly beneficial.

I have been using Selenium HQ for approximately nine years.

Selenium HQ is highly stable.

The scalability of Selenium HQ is good.

We have approximately 10 testers that are using this solution.

The initial setup of Selenium HQ is very difficult. You need different configurations on your system, such as Java and you need to configure it. Additionally, you need to have some IDEs such as Eclipse or IntelliJ IDEA on your system. Selenium is supported in many languages, such as .NET, Java, Python, JavaScript, and C#. So, at least you must be knowing any one of these languages, then only you can use Selenium.

The solution requires coding experience to be able to implement.

The deployment does not take a lot of time. You can create a continuous integration pipeline with TeamCity or Jenkins, and then you can run tests.

Selenium HQ is a free and open-source solution and is supported by Google.

We evaluated Tricentis Tosca and it was expensive and Selenium HQ is free. This is why we choose Selenium HQ.

My advice to others is the first step to using Selenium HQ is to learn a programing language.

I rate Selenium HQ a nine out of ten.

It's a very stable tool and it's open-source, and there are new versions available. The new versions come quickly and frequently, you receive a successor version with bug fixes very easily. The tool is easy to use and highly configurable.

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. 

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.

We are using a framework for Selenium HQ, which is behavior-driven. We have some features, such as login features. We write in normal English and the steps are converted into programming. We have one more feature in step definition, which connects both the feature file and step definition. In step definition, we write the program.

The most valuable features of Selenium HQ are it is open source and has multiple languages and browser support. It's very useful.

Selenium HQ can improve the authorization login using OTP, it is not able to be done in this solution.

I have been using Selenium HQ for approximately one year.

Selenium HQ is stable.

There are multiple people using Selenium HQ in my organization.

I have not used the support from Selenium HQ.

We have used other solutions previously but we chose Selenium HQ because it supports multiple browsers. If you want to check on multiple browsers using the same script, we don't have to change anything.

Selenium HQ was not difficult to set up. We can use management tools allowing us the ability to directly add dependency without having to install Selenium HQ.

Selenium HQ is a free solution.

I would recommend this solution to others if they have short projects or short-term goals, where you do not have to automate. If we have only one month for testing, we should not automate it first. If we want to automate web applications, Selenium HQ is the best tool because it supports multiple languages, browsers, and operating systems, and it's open-source.

There are multiple features the solution has that I haven't worked on.

I rate Selenium HQ a six out of ten.

I'm using Selenium for low-budget projects, small projects, and mostly medium projects. I don't use it for anything on a large scale because it has some limitations. I'm also restricted by the level of knowledge and technicality of the people I can find on the market.

The solution can be deployed on-premise or on a private cloud. We mostly do on-premise installations. We always use the latest version.

It's available open-source and free. To install it, I just have to download it. It also doesn't require too many hardware resources compared to Micro Focus. It's much lower in costs. I can do isolated projects or limited term projects. In projects where I have one shop testing, for example, government institutions or different kinds of projects where they test only once and then perhaps they continue or not, then Selenium is a good choice.

In projects where I don't have any budget and I need automation quickly, I will go to Selenium. Being free is an advantage, and it's almost at the level of professional end-license tools. It's like buying a very expensive car, like a Porsche, compared to an ordinary car. They both move forward, and you get to your destination.

I'm based in Romania, and we have a personal crisis. We do not have enough resources or enough people to employ and hire. So, I'm hiring whoever I find, and they don't always have enough technical knowledge to operate Selenium.

I've been using Selenium for about four years. 

I'm a partner and a reseller. I'm also a training provider for Selenium. We have a course which is internationally accredited and we deliver it regularly on Selenium.

It's extremely stable.

It's difficult to scale with Selenium. I would say, yes, but with a little bit of doubt, because I have to install many other products on top of it and that requires technical knowledge and time.

It is less scalable than Micro Focus. Micro Focus comes like an already made package to be scaled from a small company to an enterprise. For Selenium, I have to work on it and develop some additional things, configurations, integrations, etc.

It's an open-source tool, so there is no technical support. But there is a lot of documentation on the internet. If you study on your own, you can learn Selenium from top to bottom.

I have also worked with Micro Focus.

Unfortunately, I find it difficult. I am a nontechnical person and each time I set up Selenium, I need to read a little bit of documentation. There are too many integrations with different tools.

I would rate this solution 8 out of 10.

My advice for those who want to start using this solution is to analyze the project very well and choose the right tool for the project. For small projects, choose Selenium. It's the best option.