Selenium HQ Reviews

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 have a lot of information that we are putting on different websites and social media platforms because we need to inform our social network users about what we are doing, what we are planning to do, and what was done. Sometimes, it's information which is the same, or it's the same on different websites, in different web software, and so on. I am using Selenium mostly for this purpose.

I like its simplicity.

It would be better if it accommodated non-techy end-users. I think it's still a product for developers. That's why it's not common for end-users, and especially for RPA activities or tasks. It's hard to automate tasks for end-users. If it will be easier, more user-friendly, and so on, perhaps it can be more interesting for this kind of user. 

The second thing, when you are working in IT, you know about such tools. But if you are on the business side, you don't have much information at all.

I would like to see easy onboarding with training for end-users. Because there is a lot of stuff for developers, but for end-users, I would say none or approximately none.

I've been using Selenium HQ for five years.

I didn't have problems with stability.

I didn't have problems with scalability.

The initial setup is complex. I think some changes were done, but it's still too complicated for end-users. 

I would advise potential users to contact their IT guys because they will have a problem setting up the first automation. Of course, if there are people like me who want to develop their own knowledge, I would say they need time to get to know how to use it, optimize the process, etc. 

But if not, it will be easier for end-users to start with some kind of RPA offering by different vendors because they have their tools prepared for the end-users, for onboarding, and so on.
Because these open-source tools are still tools made for developers and IT guys, not for end-user.

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

Selenium web driver.

We were using other HP tools to automate for our website and it took a lot of memory which slows down our server response times and also slower than Selenium. We gained like seven seconds after moving to Selenium.

Though Selenium is an open source tool, I would like to see If it can support all the browsers to the latest versions and with a predefined framework tied to it. Since selenium goes with the Java there is no standard framework defined and every other company builds their own framework which is good in one way. But the skills sets requires to build this framework takes a lot of time and ROI time is also increased.

The only as I mentioned is supporting the latest versions of the browsers. The code that works in FF doesn’t work in Chrome. Scalability wise, Selenium only supports the websites with pure HTMLs.

There are lot of forums on web. So never have to worry about reaching to technical support and I’m not aware of any either.

There are lot of forums on web. So never have to worry about reaching to technical support and I’m not aware of any either.

Building the framework is the one thing and using selenium (which is straightforward) after that is much easier.

We developed in house and I totally support the In house. In house you can change your framework based on the needs with frequent code changes.

We have a great savings after building the initial framework. We run 600 test cases in parallel in virtual desktops in 16hours which takes 52 hours to execute manually. This execution takes place once in a month on an average.

We use the solution for the test automation of web solutions. It also helps us to create web browsers.  

My company uses the solution for critical deployments. 

I am impressed with the product's ability to catch content from website. 

I have found that at times the tool does not catch the class features of website content correctly. The product's AWS configuration is also hard. 

I have been using the tool for five years. 

The tool is stable but needs to update to the new version of Chrome. 

I would rate the product's scalability an eight out of ten. My company has 2000 users for the solution.

I have never used support. I would search on the internet for tutorials. 

The solution's setup is easy in the local environment but complex on the server side. You need to also update the Chrome version in the cloud before setting it up in the local environment. 

I would rate the product an eight out of ten. The product is easy to use. 

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.

We employ the version of the solution with the most ease of use, based on a search we conducted five or six years back. We now have a new client who likes the approach we used with a different one. We have a script to download the latest version, integrate it with the regression suite and then run it. Our current and previous clients equally approve of this approach. We make certain to utilize the latest version even when conducting tests during the development stage, as we find it easy to work with.

Remote server execution is a feature we find most valuable. We make use of Selenium Grid as concerns parallel execution. We also find the ordinary features of Selenium Grid to be valuable, 90 percent of our purchases comprising UI and 10 percent back-end.

In the past, we had difficulty with screenshots, but this has been remedied. We feel that all the current solutions are usable and the providers are helpful.

This said, the login could be improved, to obviate the need for relying on another one for integration with Selenium HQ. It would be nice if the solution provided an internal login system, one which would allow us to easily debug it. Until such time as a login system will be added from the vendor application, it will not be possible to identify the exact cause of a potential failure, unless there should be an interaction with, say, the UI element. Selenium HQ currently allows for an exception should an element be stale, not be found, or intractable. 

We have been using Selenium HQ since 2007.

The solution is very stable. I always suggest Selenium, even when conducting internal training. As I consider this to be a better solution than that offered by the competition and one which works, I do the same with my team. I always advocate on behalf of the ease of integration of Selenium HQ.

We have not made use of Selenium HQ’s technical support. We belong to a forum site that we joined some time ago while looking for help in finding an integration solution on the pipeline side. We were able to obtain all the information we needed from the Selenium HQ forum. Meaning, there was no need to contact anyone else with our frequent questions.

The initial setup of the deployment cycle and the process of onboarding users takes an average of 10-15 minutes. This is the length of time it takes for us to set up in our pipeline the data repositories for the regression suite, and, subsequently, integrate the data with Selenium HQ, which is the point at which we run it.

We implement the solution for our clients, not simply resell it.

The solution is very easy to implement. The first step which must be done is to go through the documentation on the site. I feel the solution to be pretty straightforward and people are drawn to it by its ease of use. There is always help available on the web for integration or implementation issues.

I rate Selenium HQ as an eight out of ten.

In my current project, we are working with an online pharmacy system, and for this system we maintain prescription details for patients. For example, patient names and other details such as where the patients live, what medications they need, and other types of information for various scenarios.

Then there is information for the doctors, such as what prescriptions there are in the system, and from which doctors they have been prescribed. These are the types of scenarios and test cases that we are automating with Selenium.

Specifically, I have been using Eggplant Functional and the Java Selenium pack, and Selenium WebDriver is the driver we use for developing the automation and scripts for the different test cases we use. This is our main testing tool for the online pharmacy system project and it is deployed on the cloud on a virtual machine because we are working from home now.

Selenium HQ has helped us through its automation capabilities, because testing manually takes a lot of time and money. For instance, we have now automated an end-to-end application for the test cases. So now it's really easy for the testers, and it reduces the time and effort taken to do their work.

There are many phases that must be completed while delivering the product to the client, and in the system integration testing phase we can easily execute our automation and scripts, which saves us a lot of time and enhances the testing process dramatically.

There are many useful features in Selenium that I like, and of the new features I particularly enjoy the Selenium Grid. With this, we can run many test cases in one go, and in one suite we can extract multiple results.

Because Selenium also supports parallel test execution, I believe it is one of the best testing applications out there.

Beyond the many advantages that Selenium HQ brings, there are also several disadvantages. For example, there are some complex scripts which can make Selenium unreliable in some cases.

For email-based applications, we can't automate as we would like to, making it necessary to bring in a third-party product to do so. Eggplant, for example, offers email-based processing, like with the OCR engine, and for automation testing and reporting I would like to see a similar feature in Selenium.

I've been using Selenium HQ for at least one year now. 

I find it a reliable solution for the most part. But in some cases it is only as reliable as the third-party code it works alongside with. For example, Selenium doesn't have automated generation code, so we are dependent on other tools for this. And as I have mentioned, we also need to use third-party tools for things like email-based applications.

Selenium HQ can be scaled with the use of parallel test execution, and when it comes to expanding its use more generally, it's possible to add on to its automation functionality with third-party tools as well.

For our work with Selenium, we have a support team that helps us so we can go through them when we have problems. But for the small things, we generally solve problems ourselves. We are able to do self-study when it comes to support, and we also have a tech support architect who is able to help when needed.

The initial deployment was simple, as we are not doing anything too complex with it. We're using Azure DevOps for the deployment, so we test for that with a test plan and build up the pipeline accordingly, so we can execute and get the test execution report in order to find out what other test cases were impacted, and what other test cases we need to resolve. Doing it this way, we can easily find and fix any bugs in the deployment.

We have built up some custom implementation strategies when it comes to our daily use in Selenium HQ. For the test cases, we first verify which test cases we need to automate by coding some common functions, like logins and other common functions that are present in the application. After that, we look at the locators we will need to select using XPath, and then we start building the test cases according to the specific application, using code from all the common functions.

In the implementation team, we have six people who are using Selenium HQ for our current project. There are more people in other projects that I have running, but for this one there are only six of us. One or two are technical leads and the others are project engineers.

When it comes to maintenance of Selenium, we leave that up to others. We are mainly responsible for automating all the scripts that we deliver to the client.

Selenium HQ is open source and our use of it in our company is provided for free.

I would surely recommend others to use Selenium as we do, especially because while using Selenium we can use Java concepts as well. It's great that, through Java, anybody can use Selenium; even novice programmers. In today's market, automation is a big part of every organization, and Java programming skills can hugely enhance the use of tools like Selenium.

One of the biggest lessons I learned was during my time as part of the development team. I didn't want to work in the manual testing team and so when my development project was completed, I moved to the automation department because I wanted to carry on being productive. With this move, I realized that I could easily learn other tools and technologies that are useful in the market, by adapting my programming skills in Java, Python, or any other programming language, to working with tools such as Selenium. In addition to my Selenium work, I also now do Rapid Automation as an automation engineer.

I would rate Selenium HQ an eight out of ten.

• Automate test across several browsers such as IE, Chrome, Firefox and Safari
• Write automation scripts in any language of your choice Java, C#, PHP, Python and many more
• Ability to execute tests in parallel which provide time saving for testing
• Ability to take screenshots of every tests
• An open API that can be extended based on our needs
• A Recorder Tool to record tests and execute them for non-developers

We provide IT services and solutions, and this solution helped our clients reduce their manual testing efforts to greater level. Our clients have realized benefits by reducing their testing cycle from three days to three hours through Selenium.

They can improve test reporting, and more importantly on test scripts, by providing less constructs to automate more complex testing scenarios.

I've used it for the past nine years. We use it alongside Appium.

Deployment is little tricky but with good help from external vendors organizations, can implement a Selenium based test automation solution in a short period of time.

There have been no issues with the stability.

There have been no issues with the scalability.

There is great on-line support from the users community. External vendors have innovative solutions build using these tools where they provide tremendous support.

It was difficult to some extent, but with good documentation from the on-line community we where able to implement the tool.

We did it in-house. If you are implementing it for enterprise level its better to seek external vendor help.

We have seen ROI of more than 60%. It's open source.

I would say start lean, gain small wins and incrementally add more. Example: Start automating test cases for one browser and slow expand to multiple browsers.