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 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.

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.

Currently I am doing mobile application automation with Appium and Selenium, as well as front-end application automation with tools like WAVE for mobile and desktop applications. The only area that I'm not involved in at present is API testing, though I am hoping there will be opportunities to get to that as well in the future.

We typically use Selenium and Appium in automation and testing by first identifying which modules we are able to automate. Then, whenever we encounter some new course in the framework that we're using, and we need to use a hybrid kind of framework, we will use Selenium to resolve it. 

Selenium has improved the way we work because if you do what we need to do manually, you'll have to expend a lot of time. For example, it would be a huge chore to navigate through an application manually every day, and particularly if there's a new build on the way, you would have to check all the regulations over again by hand. That would simply take too much time, and so what Selenium does for us is that in one resource it can handle the work of three, four resources, provided that the scripts are straightforward and coded properly. That's the main cool thing about Selenium, I would say.

For me, the most valuable feature of Selenium lies in its ability to help us find elements quickly. Apart from that, the driver interface is really useful, too. When we implement the Selenium driver interface, we can easily navigate through all of the pages and sections of an app, including performing things like clicking, putting through SendKeys, scrolling down, tagging, and all the other actions we need to test for in an application.

One drawback to Selenium is that there is nothing like an object repository, such as that found in QTP, especially considering continuous integration practices that have become common nowadays. In future, if they can provide an object repository or some kind of repository for data, then that I would greatly appreciate it. For example, once you have the app credentials and all the other security data and you don't want to show them to other people who are not authorized, a repository for this kind of data would be very useful. You could then simply grant access to only those people who need it.

Another improvement I can think of is in the area of documentation and support. With Selenium, we're using freeware software, and because of this there is no support or anything from the vendor. In this case, you have to rely solely on your own coding experience and exposure to the tool, and you often have to search through many pages of code when you want to change something in your implementation. It also makes you rely on your problem-solving skills to a large degree, because some problems are not that easy to solve by yourself.

If I can compare Selenium with another solution such as SoapUI Pro, there's a big difference when it comes to coding your own solutions. With SoapUI Pro, if you want to fetch some data, you don't need to write any code or anything, and for someone with no coding experience, this makes it much easier to be able to use effectively. So, ultimately, more support for non-technical people would make for a great improvement in Selenium.

I have been using Selenium HQ for the last two to three years.

The stability of Selenium depends on the skill level of the team that is using it. If you are writing solid code for automating your scripts, then you will find that Selenium itself is a stable solution. But if you're writing sloppy code then you may find that Selenium slows down or becomes unstable. Truly, I think it all depends on the people who are using it, and how they approach the architecture of the framework.

I am hopeful that Selenium will scale well because, along with others nowadays, we plan to to move into cloud-based provisioning with continuous integration. We will be doing that with AWS, most likely.

I haven't taken any technical support till now because Selenium is freeware, and you will not be getting any technical support directly. So that could be something that they could work on because if they were able to provide support, it would great for us and many others. Without it, you can still add code to the Selenium software itself, but they won't be able to help you with it.

On the other hand, I do believe there is enough documentation online for anyone who wants to figure it out by themselves. There are videos, tutorials, and other resources available to us.

The setup of Selenium is easy, in my experience, since it is provided as JAR files that you can download. Apart from that, there is, I believe, an architectural approach where you can simply input your dependencies and it will automatically download all the JAR files needed, and other required files.

As for deploying the code, this is just as easy. For example, if you're working with some type of continuous integration, it's a breeze to deploy. First, you have to build up your framework, and then you can deploy it to Git, or GitHub, or anywhere you want. At this point it's just about uploading the code, so there's not much to it. 

I am currently implementing Selenium along with a few other tools. For example, for mobile device automation, I'm using Selenium with Appium. The Selenium architecture can be integrated with Appium in order to be able to automate with mobile devices such as Android and iOS, which is what I'm doing now. Beyond that, we also have desktop applications; for Windows we have EXE files and for Mac we have DMG files. With these, I have implemented the Windows application drivers using Selenium so that we're able to easily automate any Windows-based or Mac-based app.

As for the rest of the team who are implementing Selenium this way, we have about 15 people on the testing side of things, and 6 people in automation.

Selenium is free software so we do not pay licensing costs. 

My advice to others is that, first of all, you have to understand the process of automation from a general point of view, and how people get on with the coding and all that. If you only have manual experience, like a lot of new testers, then you likely don't have much experience in coding either. And in that case, my advice would be to first understand the logic of the process. For instance, before jumping into it from the deep end, try get a handle on a few small steps first, and as you go along you will learn the basic coding, the basic architecture, how Selenium works, how the automation process works, and so on.

Then, take a piece of code and ensure that it works as a standalone script, then finally jump into the framework. Develop from any framework, use it as best as possible, get some experience with it, and try to become an expert from there.

You can use any programming language you prefer. As for myself, I'm using Java, but you can use C#, Python, Ruby, PHP, etc. There's a lot of support for different programming languages with Selenium. 

My biggest lessons while using Selenium have had to do with automation and how it really works, which is something I've always been interested in. Once I get an application, any application whether it be a WAVE app or mobile app, I very much enjoy getting stuck into the automation part of testing. And what I've learned is that not everything is that easy to automate.

In many cases, I have had to team up with new solutions and play around with code on my own, which has been a great learning experience for me. Apart from that, with Selenium I have been able to implement new things such as OCR (Optical Character Recognition) which is useful when you are not able to find all the elements you need, and I feel good that I was personally able to enhance the automation process with what I have learned along the way.

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

My company started using Selenium HQ two years ago for unit testing. We were trying to evaluate the record and playback features. We are basically outsourcing this function, and we're charged for every developed feature and testing. So, we thought that we could test it ourselves using the record and playback feature. We were navigating our web application records in a macro and tried to reproduce that later. But for some reason, it's not the best solution for us.

I like the record and playback features. We also appreciate that it's not just writing on a script that we create. While we were browsing our web application, it automatically records all the clicks and movements of points. We also appreciate the fact that it provides screenshots of everything in the output.

It would be better if we could use it without having the technical skills to run the scripting test.

I think we have been using Selenium HQ for two years, but I only joined the company six months ago.

We are satisfied with its stability.

We are satisfied with its scalability. We have five or six users working with Selenium HQ.

Selenium is an open-source solution, and It's free.

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