Selenium HQ Reviews

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.

I mainly use Selenium for web applications.

The most valuable features are ExpectedConditions, actions, assertions, verifications, flexible rates, and third-party integrations. I also like that it's an in-house solution, which means you're not dependent on any tool.

I find Selenium to be slow - its server takes a long time to interact with your browser and sometimes fails. It's also somewhat outdated, for example, it has no capacity to handle things like desktop pop-ups, does not support mobile testing, and has very limited reporting. In future releases, I would like Selenium to focus on headless execution when executing their test cases, using PhantomJS or Chrome Headless.

I have six years of experience with this solution.

There are issues with scalability in that it requires a technical person to perform it and takes a lot of time.

Selenium is open-source and has no technical support, but there is a big online community on platforms such as Stack Overflow who provide help for users.

I've previously used Node.js and Cypress.

Selenium is comparatively difficult to set up and requires technical knowledge in order to integrate and configure it. I developed a complete, fully-functional framework for this solution, which took around eight months to automate around 100 test cases.

In Selenium, you have to write extensive code - even if you want to automate one login scenario, you have to write a code of around 50 lines - which uses a disproportionate amount of man-hours. It takes such a long time to use this solution that it may be worth looking into other free solutions such as TestProject or Katalon Studio, or paid solutions to replace it.

Before implementing Selenium, I think it's very important to find out the maximum resusability of the code using the parameterized XPaths.

I would rate this solution as seven 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.

Depending upon the functionality, I use Selenium to prepare the scenarios I'm doing. I start by writing automation scripts in Java. From there, we execute the scripts if there are any changes in the product. Then we upgrade this overnight along with Jenkins to make sure our application is running as expected. They feature continuous deployment and continuous integration with the help of our teams, so our product will be applied to more users once it's adequately tested.

Selenium is the fastest tool compared to other competitors. It can run on any language, like Java, Python, C++, and .NET. So we can test any application on Selenium, whether it's mobile or desktop. And if I build some framework on Selenium, I can give it to someone else. Then they can use it and start going further. One more thing is that you can implement any framework on it, like TestNG, Cucumber, JUnit, etc.

Selenium should implement more islands for a desktop feature. My laptop and desktop have a calibrator or some other desktop applications. We can automate those things through Selenium, so they should be adding them in the subsequent versions. For now, I guess Selenium could add some other features like object communications for easy expansion. 

I've been using Selenium HQ for about five years.

So performance-wise, Selenium is the best tool so far. It has the fastest automating tools.

We run scenarios at midnight or around that time and split this application into virtual machines. So during that time, the application is executed in panel mode. Let's say I have 10 vital missions in the Google Cloud Platform. These things will be triggered automatically and executed in each of the machines. And it has a balancing load concept, so if one machine is at capacity, it will automatically move to a second machine for the other scenarios. So there is never an issue with scalability. We have more than 1,000 employees in the company using it every day to develop scripts. 

Because Selenium HQ is open source, we don't have a customer service team or technical support, so we have to search on our own for answers. When I've had problems in the past,I've had to Google to see if it's an application issue or a Selenium issue. Without any help from vendors, it's difficult to automate some things like CAPTCHA. But still, we have a framework that is ready for this. So with the help of this framework and importing those library files, we can make our own way. 

At my previous company, we used a UFT tool called Micro Focus UFT. We used this because it was a different kind of use case where we had to transfer our publications back and forth between the mainframe and the mobile application. So we have to format that, which is why we used the UFT.

Setting up SeleniumHQ isn't that complex. We like to develop our application in Pega and have a point cloud that we deploy on Google Cloud. It is developed and tested with Jenkins, which is a continuous integration tool. Once the code is specific to Jenkins, we trigger Selenium and execute the scenarios. After this finishes, we move everything to cloud. 

Along with this docker, there is a deployment phase in Google Cloud, where the images of our application are moved to pre-production. Pre-production is something like a replica of production that allows the users to work on it. So once it is transferred to pre-production, the users will work for one week or one or two. If they are satisfied, we move on to production.

Deployment usually requires about eight to ten people. Most of the work is done by technicians who are akin to database administrators. They take this on for one month a year every year. Their job is mostly to minimize the weight of the application. In the next phase, DevOps engineers deploy the enviornment. The time for deployment depends on the teams and the tasks. If there is a small change, it may have taken between half an hour and an hour. On the other hand, if there is a significant upgrade of the application, it may take eight to ten hours. Generally, we don't need any maintenance unless a UR application has changed.

Selenium is free. Anyone can use it without paying anything.

I rate SeleniumHQ seven out of 10. When you're choosing a solution, it depends upon the type of applications you are using in your project. If you have only have desktop and mobile, go for Selenium. However, if you have multiple applications like Windows-based applications, a virtual machine-based application, or a mainframe .NET application, I suggest going with another tool, like Tosca UFT.

We are still testing Selenium HQ.

The client is based in the U.S. They process the code checking, and we work on the script.

When we get storage or requirements for manual testing, we begin the automation once it is stabilized.

We work in the healthcare domain.

If for example, I get a diagnosis for a particular patient, it continuously changes as there are at least 100 sets of data. It's impossible to make that work for each and every build manually. The parameterization and parallelization have helped us with the inputting. 

Every week we have reviews. We have automated the stabilized areas. It has helped us to add speed to our cycles.

Data parametrization and parallelization are the most important features in any automation tool.

Speed is very important for continuous integrations and deployments. The team gets more time to focus on other new areas.

The configuration of different data sets is also very important.

With Selenium, it is an open-line, I can integrate at any time, from anywhere.

There are some network issues, as the line is not very clear.

There are some areas that need improvement. I continuously see failures in threads when it  is running in parallel. 

I find that it fails, especially when I use APM automation on the mobile side. I have experienced these issues, and since the APM is also based on the Selenium pack.

It is a challenge to locate them, or knowing the location of the unique elements on the APM application. I don't see many issues with the Web applications but there are several with the APM.

As an open-source solution, there is no dedicated support.

Extending functions on the codes would be very helpful.

I have been working with Selenium WebDriver for four to five years but in the last year, it has been working mostly on the functional testing.

There are some issues with the stability of Selenium HQ.

In terms of scalability, we don't use many distributed systems. It is for a limited number of users. We have one lead architect and three senior QAs.

We don't deal with technical support. Our clients handle that on their end, but there is no direct technical support.

I have some experience with Selenium WebDriver and Rest Assured API automation. 

In regards to mobile automation, we use Appium.

Six months ago, I work on Selenium NUnit.

Clear instructions were provided to complete the installation. It was very straightforward. There were no issues when installing this solution.

APM setups are a bit more of a challenge. It takes longer to set up APM.

There were no issues in the installation of WebDriver. From the end-to-end process to deployment, to the automation code.

We have one dedicated assigned person for continuous integration and deployment. We check in with him before we complete any code. We provide him with our test and script, and the integration is done with him present to avoid any issues.

Selenium is open-source. There are no licensing fees with Selenium.

We are currently evaluating functional testing tools, both manual and automation testing.

We are looking for codeless automation with support for codeless automation.

In my evaluations, I have seen that some are tools are lacking.

I have worked full-fledged on Selenium WebDriver along with the multi-tenancy for the JavaScript framework.

I have hands-on experience with the Selenium framework, and I also worked on, API for APA automation Currently I am working in the healthcare domain.

In my opinion, it is a complete end-to-end solution.

As of now, it's for only web APIs. It provides a complete solution. 

I don't see that it's many disadvantages, except when doing the coding. A person should have perfect coding skill sets. If they don't have a coding skillset, it's a little difficult for them to get started. 

We had completed multiple POCs to present to our clients.

It was pretty straightforward for me. I didn't experience a lot of difficulties getting into Selenium. If your framework with Selenium is good, then it gives you the correct output.

I would rate Selenium an eight out of ten.

My customer previously validated every file and it would take almost 15-20 minutes for a document. They used to randomly select and test only 100 out of the thousands, maybe 85,000, files, to pick up sampling. Each file would take around 20 to 25 minutes, so we were not able to do it manually, but with the help of Selenium, we were able to test all the files in two days. It saves a lot of time.

Selenium HQ is open source, which is one thing that I like about it. Whatever you want to find, it's already there. If you'd like to add some features, you can. You can also contribute to it. Whatever problems we face, we can go and add. It is most like Eggplant, which is a paid tool, but here we don't have to pay for anything.

In terms of what could be improved, there are some glitches with it, but whenever you report it, the open source community works on it and fixes it. There is no support here. If I say in the user community that it's not working, I have to go and check Openstack and extract questions and answers from the community. There is not any company that is supporting it that could help me. There is no particular documentation about it that can help me in a technical way. I would have to see people's user experience and see what they have done in such and such scenarios.

Sometimes we face challenges with Selenium HQ. There are third party tools that we use, for example for reading the images. They are not easy to plug in. The third party add-ons are difficult to get good configuration and do not have good support. I would like to see better integration with other products.

In the next release, I would like OCR, image recognition, to be built-in. Sometimes there are no code elements that are detectable so finding x paths is tough. Whenever there are some challenges here, we could use OCR or something similar, with good image recognition.

I have been using Selenium HQ for the last couple of months.

Selenium HQ's scalability depends on the modularity of the product. Our product was more modular. When we made the product testable for one document, we were able to test 20,000 documents with it. So the scalability was quite impressive.

We have three people in the testing team who are using it.

We are considering expanding usage. Since it has reduced the business time, there are new scenarios that other business teams were using it for. So they asked us to include those scenarios as well, reducing the time.

There is no tech support because it's open source in Selenium.

You just have to raise the bugs in the community and if someone has time, they can fix it. So it's not so quick.

The initial setup was straight forward. We don't use it in deployment, we just use Selenium for testing in our organization. The code which was deployed was tested before.

There are four developers in my team who are working on it.

It was not a Selenium deployment because the deployment was of code, and we only use Selenium for testing purposes. We did not deploy with Selenium code anywhere on production.

In terms of pricing, it is open source, so we don't have to pay anything for Selenium.

My advice to anyone considering using Selenium is that using their libraries is good but the focus should be on finding the elements. Element location is a tough part. There are plugins that are available so don't waste time creating your own locators. You can use ready-made built-in solutions that would reduce your time a lot.

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

We primarily use the solution as a functional testing tool.

Selenium is a freeware tool, through which I am using Java for automating our project testing and with its feature grid and a different browser, I can do the functional testing. We can automate our functional testing through a browser. It supports all types of browsers including Firefox and Chrome.

We can run multiple projects at the same time and we can design both types of framework, including data-driven or hybrid. We have got a lot of flexibility here.

It's easy to customize according to our needs. 

Now we are getting lots of extensions such as BlazeMeter, where you can record and generate the script and modify, et cetera.

The initial setup is easy.

The parallel testing in Selenium is lacking.

The latest versions are often unstable. 

There's no UI in Selenium. Beginners who want to start using it must have knowledge of Java, Python, or any programming language. If you are using a Chrome extension, that is a BlazeMeter extension, you can record and make the script, however, that is not very helpful for beginners.

The editor is based on Eclipse. It would be nice if there was some in-built UI for this.

I am leading a 20 person team where I have some junior staff and we have to set up lots of demos and training for them to be comfortable with Selenium.

Occasionally, if someone is downloading the latest version of Java, it might not align with the Selenium version. There needs to be a way for Selenium to alert you if there will be a conflict between versions. 

I've been using the solution for four years. 

The level of stability depends on the version you are referencing. For example, Version 3.1.46 is very stable, however, Version 4.0.0, the latest version, is not.

There is no technical support available for Selenium, as it is an open-source product. There is a blog where you can find answers to questions, however, there's no one to actually reach out to. 

Previously, I was using VSTS Ultimate.

The initial setup is pretty straightforward and simple.

You first have to install Java, JDK, in your system. Then you can install an editor such as Eclipse. In Eclipse, you can incorporate all the Selenium jar files.

The solution is free to use.

The reason we are using version 3.14.1 and not the latest version is that this version is the latest most stable option. The most recent versions are often not the most stable. 

I'd rate the solution at a six out of ten.

There are lots of tools in the market that are paid versions, such as QTP. Those have got lots of features. While Selenium has some good features, due to the fact that it's free, you cannot get support, which is why I have reduced my rating by a few points. 

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.