Selenium HQ Reviews

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.

We do UI-based functional testing in Selenium. We have prioritized some of the use cases that are most likely to be affected, and we have added those to our regression suite. Each week or each month, we trigger the regression suite to check that nothing is broken.

It supports many external plugins, and because it's a Java-based platform, it's language-independent. You can use Java, C#, Python, etc. It's open to different platforms, but you have to be really good at coding to work with this.

If they can integrate more recording features, like UFT, it would be helpful for automation, but it's not necessary. They can also add a few more reporting features for advanced reporting.

I have been using this solution for the last four years. 

It's a stable product.

It's scalable. If you have a Jenkins setup and you are running on the grid, it's robust and smooth.

We have about 300 users, and it's used on a daily basis.

We have mostly used online support. Whatever you're looking for, the answers are already available on the web. If any technical issues are there, our own internal IT team is also able to fix them. I don't remember any instance of connecting with their support. So, it has been really smooth.

Positive

Its initial setup is a little tough. It could take around six hours, but if you are experienced enough, you can do it within an hour. If you are a complete beginner, it will be a little difficult.

You have to be really good with the POM dependencies, and you have to be used to working on different IDEs, such as IntelliJ or Eclipse ID. Based on the different setups, you have to consider the POM file and also integrate those dependencies. These things take up some time initially, but once they are done, it works well. I would rate it a 4 out of 5 in terms of the setup.

It doesn't require much maintenance. If you are upgrading to a new version, the basic changes will be needed, but not that much maintenance is needed. It's really easy. They do a release every six or seven months.

Selenium is an open-source product. It is free.

It's one of the best tools I have worked on. It's a strong tool and a winner in functional testing and automation testing. It's open source, and it also supports mobile testing. Other tools, such as UFT, are quite expensive. 

I would rate it a 9 out of 10.

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 Selenium HQ for the web application we developed here.

Some of the most valuable features of this solution are open-source, they have good support, good community support, and it supports multiple languages whether you use C-Sharp or not. These are some of the most important benefits.

Katalon has built a UI on top of Selenium to make it more user-friendly, as well as repository options and the ability to create repositories for objects, among other things.

It would be helpful if this type of information could be included in the Selenium tool itself, so people wouldn't have to do filing testing.

I have only been with my current company for a short time. It has not been a long time since I have been working with Selenium HQ.

We worked with the open-source version of Selenium HQ.

Selenium HQ is a stable solution.

Selenium HQ is scalable.

There are approximately ten people who are automation engineers from level one to level four using this solution.

We have community support because it is open-source. There is no paid or dedicated support.

We're just getting started with Katalon, and it's our first time using it.

The initial setup is very simple.

Maintenance is required. 

The scripts we must maintain require a significant amount of upkeep.

It was open-source.

It's a free solution, we don't pay for anything.

It is an open-source product, it is free for anyone to use.

We were doing a proof of concept to see which tools we could start using for our team.

If it is not a large project or application, Selenium HQ is a good choice; however, if the application is large and you want to maximize coverage, I believe you should look into tools like Katalon or Ranorex, or something that allows you to do more scripting with less coding.

I would rate Selenium HQ a seven 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. 

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.

I have led regression testing projects involving CRM, employee registration, and eCommerce. In each of these test cases, we have used the automation tool which has brought us benefits in time savings, shortening schedules, or recovering lost time - all of this leading to money savings. 

It's very useful when there are constant changes in the back-end. If the changes are constant in the source end it is not a good idea to use it. It is very important to previously evaluate the use of the tool depending on the characteristics.

The main improvement is the lower cost of regression tests. It will probably be more expensive in the first iteration (more or less 30%), however, we can save up to 40% or 50% in the next runs. 

Another benefit is that, once the test scripts have been built, it is not necessary for the person executing the test processes to be an expert, allowing resources and costs to be optimized with lower costs in human talent. 

In addition, the barrier of functional knowledge is eliminated; specialization is not necessary during the life cycle of the tests.

The main characteristic that is useful is that the tool is completely free.

Additionally, currently, you can find resources that handle the characteristics of the tool very well. 

The range of web platforms it supports is also wide, including the operating system platforms. It is possible to reuse the test scenarios that have been built in iterations after the first one or in the improvements of the systems that are part of the normal maintenance and updating that must be done periodically and that imply an investment in tests.

A great improvement could be in the user experience which is necessary as it does not have much. The use is too technical; it is not designed for the end-user. The best way to maintain the test scenarios over time should be considered. If the test scenarios are not subdivided correctly, it is very likely that maintenance will become very expensive and re-use is unlikely. This would ultimately mean that it would reflect the possible benefits in the projects and, on the contrary, the use of the solution ends up being more expensive.

I have been working with Selenium for five years.

The latest version should always be treated with care. Being open-source it can be unstable.

The scalability will depend on where the tool is installed.

Until now, I have not used the support service. Everything has been done using the documentation that is registered in the forums.

Neutral

In the past, I used a very good solution. However, it had a high cost and had to be used by more than one resource.

The initial setup can be very complex.

In my case, the initial setup was done internally.

The ROI can be between 20% to 50% in the testing process in the medium and long term. In the short term, it can be 10% or less.

As for the license, there is not much to say. It is free, however, the configuration must be done correctly or it can be very expensive.

Other options that I evaluated were TestComplete, Kathalon, and IBM.

It must be evaluated very well before being used. In my case, we implemented a front-end that facilitates the use. If you want to use it in the future I can give you some access.

The primary use case is web automation.

It has an extension available called Appiam that we use for our mobile automation.

The most valuable features are that it's open-source and the community support is good.

This is a product that does the task for us and it's easy to use.

Coding skills are required to use Selenium, so it could be made more user-friendly for non-programmers. If you purchase Katalon Studio, then it comes with an interface for Selenium.

If there were other tools or companies that integrated with Selenium then it would be helpful. At the moment, it's just Katalon.

It would be helpful if there was an organization that we could reach out to, in order to get support for the product. As it is now, you have to find help yourself. For example, you may have to use Google search to look for similar issues and discover how they were resolved.

I have been using Selenium HQ for between two and three years.

The stability and performance are good.

This is certainly a scalable product. However, based on our requirements, we haven't had a need to scale. It's used in-house and at the moment, there are only five people who use it.

It's a standalone tool, so you put it in one place and everybody uses the coding scripts that you write.

We do have plans to expand our automation capabilities, and if so, it will expand our usage of Selenium.

We are using the open-source product, and they do not have a dedicated support center. Instead, you have to look for online forums and you always find people that are willing to help you. That said, you have to do some research on your own.

The initial setup is fairly easy. It requires you to install their IDE, which is Eclipse. In total, it takes between three and four hours to deploy.

We implemented this product in-house. It does not require much maintenance.

This is an open-source product that can be used free of charge.

This is a Java-based product so the version is tied to your version of Java.

Overall, this is a good product and I recommend it. It is easy to use and works well once it is set up, although support requires research and you need to have some coding skills to use it.

I would rate this solution a seven out of ten.