Selenium HQ Reviews

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.

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.

the primary use cases of this solution are UI regression testing and API automation testing.

The most valuable features of this solution are its flexibility, being open source, and it has close to no limits when it comes to integrating with any language, or browser you are using.

The solution can be improved by providing better reporting logs.

I have been using the solution for four years.

This solution is the most stable product I have used when it comes to web automation.

This solution has no scalability limits.

The initial setup is easy, like a walk in the park for any user.

I implemented the solution in-house.

The solution is open source.

Before choosing the solution I evaluated Cypress and Postman. 

I give this solution nine out of ten.

When it comes to UI testing this solution is perfect but for API automation it lags behind compared to Postman.

Around 70 percent of our engineers use this solution on a daily basis.

Since the solution is open source you can create a user account on GitHub and receive free community-based technical support when it is required.

The 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 use Selenium HQ for web automation. We are using C Sharp for development.

Using Selenium HQ helps us by executing tests quickly. It saves us time and reduces the need for manual testing of repetitive tasks, thereby reducing efforts.

The most valuable features of Selenium HQ are that it is free and allows using any programming language. Additionally, it supports different frameworks that are suitable for various projects.

There is a challenge with concurrent testing, where parallelization is not fully supported. Sequential tests depending on each other cannot be executed in parallel. This feature could be improved.

I have been using the solution for more than two years.

The stability of the product is good. There are no major issues.

The scalability rating would be around a seven to eight out of ten. There are still challenges with parallelization and testing.

There is enough help available online. Simple questions and repetitive tasks have a lot of available resources. However, finding help for customized scenarios can be challenging.

Positive

The setup process was simple. I managed to complete it by myself.

There are many products that depend on Selenium HQ. Protractor is one of them.

I'd rate the solution seven out of ten.

I use Selenium HQ to create automated scripts for automated applications.

Since Selenium HQ has multiple plug-ins, we can use it with multiple tools and multiple languages.

I rate Selenium HQ a nine out of ten for stability.

I rate Selenium HQ a nine out of ten for scalability.

The level of ease to set up Selenium HQ is medium. You need to have experience in order to do the initial setup.

Selenium HQ is a free, open-source solution.

Selenium HQ is deployed on-cloud in our organization.

Overall, I rate Selenium HQ a nine out of ten.

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

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

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

I have been using Selenium HQ for approximately one year.

Selenium HQ is stable.

There are multiple people using Selenium HQ in my organization.

I have not used the support from Selenium HQ.

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

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

Selenium HQ is a free solution.

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

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

I rate Selenium HQ a six out of ten.

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.