Selenium HQ Reviews

Selenium HQ is an automation tool for automating applications. 

Selenium HQ is primarily used for smoke tests, and its excellent stability allows such tests to be executed seamlessly. The solution helps in regression tests where certain scenarios need to be repeatedly set. Manual processing of regression tests is highly time-consuming, but using Selenium HQ can reduce the time effectively.  

I believe Selenium HQ to be the best solution in the market for automating web applications.

There are some synchronization issues with Selenium HQ; often, the solution is unable to match the browser speed, which has led to poor results. Some mechanisms should be added to Selenium HQ to improve synchronization. 

It's an open-source solution with regular updates, but previously, in the 3.14.0 version at our company, we had to setup the ChromeDrivers, but in the latest feature, it wasn't necessary as the solution got easily integrated into the cloud. 

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

I will rate the stability an eight out of ten. 

I would rate the scalability a seven out of ten. At our organization we have a team of five or six people who are using Selenium HQ for automation. The maintenance of the product is always costly and time-consuming. It's very difficult for anybody to understand the code in business logic for a third party, so in our company, we need to share our knowledge with the maintenance professional first. 

To know about any updates on Selenium HQ I use search engines like Google and then update my Selenium HQ version accordingly. 

It's an effortless process to setup Selenium HQ. As part of the installation process, the dependencies need to be downloaded and pasted into the XML file for auto-execution. The installation of the solution can be completed in a few seconds. 

In our organization, we use Atlas for IDE and Maven for Eclipse to copy the dependencies from the cloud, and the rest of the testing process is setup using a test engine. 

For testing web applications using Selenium HQ, the panel application and test synchronization features have proven the most beneficial. Selenium HQ supports almost every project browser, like Edge, Firefox, and Chromium, for testing automation. I would definitely recommend Selenium HQ to others, it's a robust product for automating applications. 

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

Selenium's major use cases are UI and web automation, primarily for the front end of a website. We also use it for API automation using other libraries called RestAssured. The programming language can be Java, C Sharp, or anything, but we are mostly using Java. For mobile automation, we use Selenium with APM.

Productivity-wise, Selenium helps us in regression testing, which we need to repeat every sprint and during every release cycle. Though development may take some time, we are now utilizing AI tools like ChatGPT, which makes it faster to develop the code. Cost-wise, it provides savings because it's open source, so we do not have to bear any cost of the tool itself.

Selenium is an open-source tool. It provides the flexibility to automate anything and everything. You can build custom libraries and integrate them with third-party libraries across the globe. It gives freedom to integrate with any other tool and build your custom solutions. It also integrates well with test management and project management tools like Jira, Manta, and Azure DevOps.

In the future, Selenium should be able to automate desktop-based applications, as it is not currently able to handle non-web-based, Windows-based applications. Additionally, there is a need for Selenium to be more user-friendly, allowing users from all backgrounds to automate test cases without requiring too much coding knowledge.

Selenium has been in use for more than 14 years.

For stability, I would rate it a seven out of ten.

I believe Selenium is scalable, and I'd rate it a nine out of ten.

There is a community in which you can post your questions, and you do get answers there.

Positive

Recently, I worked with Katalon. Then, I worked with WebDriverIO with Node.js.

The setup experience is much easier these days. You no longer need to manually download dependent files like JAR files. You can easily go to the Maven repository and get all of the dependencies. Setup has become more straightforward, and I would rate it around seven out of ten.

Being an open-source tool, Selenium's cost is completely free, and there are no licensing fees.

In addition to Selenium, we are using Playwright and Myspro for mobile automation in different projects.

For users starting with automation, I recommend learning Selenium with any language they're comfortable with, such as Java, C Sharp, Python, JavaScript, or Ruby on Rails. It sets up a foundation for any tester wanting to explore automation testing.

I'd rate the solution eight out of ten.

We are using Selenium HQ for the automation of web applications.

The solution can be deployed on the cloud or on-premise.

The solution has improved the company by reducing a lot of manual work.

The most valuable feature of Selenium HQ is the ability to configure a lot of automated processes.

We can only use Selenium HQ for desktop applications which would be helpful. We are only able to do online based applications.

I have been using Selenium HQ for approximately three years.

Selenium HQ is a stable solution. However, it depends on how the applications are identified. If the applications or objects are identified correctly then it is stable. Otherwise, we can have some glitches in the identification and verification.

The scalability of Selenium HQ is good. It can be scaled. There are some robotic files that can be added to scale up the solution.

We have approximately 2,000 to 3,000 users using this solution in our company.

Depending on the project we are involved with, we could use the solution daily, weekly, or monthly.

We use forums and documentation that are helpful for troubleshooting.

If you only look at the web application automation from Selenium HQ compared to other tools, such as WorkSoft and UFT, the speed of execution is very slow in WorkSoft and UFT. The scalability with multiple browsers is simpler and easier in Selenium HQ, whereas it's a bit more complicated in WorkSoft and UFT.

Selenium HQ's initial setup was straightforward. However, the integration part took some time.

I rate the initial setup of Selenium HQ a four out of five.

Selenium HQ is a free solution.

This solution is good to use if the application that is getting identified for the objects is able to uniquely identify the properties. If this process works well then it is good to use. If it is a web application, they can use this solution, but if a desktop-based application is involved, then they should look for another solution.

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

We use the product for mobile and API testing purposes.

Selenium's open-source nature is a key advantage. Its extensive support for diverse web technologies. We can combine it with APM for mobile, API, and web testing.

They should leverage the tools for supporting Windows apps. Additionally, they could add more customization features for reporting.

We have been using Selenium HQ as partners for nine years.

The product is stable. However, it is impacted by the changes in UI. I rate the stability a seven out of ten.

We manage Selenium HQ for 20 customers. It is a scalable product and suitable for small to medium enterprises. It needs improvement in terms of supporting Windows devices.

I rate the scalability a seven or eight.

It is an open-source solution, and thus, we do not receive direct support services. We refer to relevant documentation and community articles to resolve most issues.

The initial setup for mobile app testing, especially when installing simulators, is complicated. Configuring simulators for Android and iOS platforms is time-consuming due to trial and error. Setting it up for mobile automation takes approximately one to two weeks. However, for web automation, the process is comparatively straightforward. It takes less than an hour to complete.

I rate the process a seven out of ten.

It is an open-source solution.

It's crucial for technicians to thoroughly evaluate whether the solution aligns with the end-to-end application needs, especially considering the complexity of enterprise applications. For leveraging features like ERP integration or mobile testing, it is better to understand the compatibility and support for specific devices.

I rate Selenium HQ a seven out of ten.

We primarily use the solution for normal regression tests.

I like most of it. It is possible to get a lot of help and find help on the internet since Selenium is so widespread and established. The documentation is great.  There is  a lot of help on websites like Stack Overflow.

It is very stable.

The product is open-source. 

We are thinking about codeless automation, like what ACCELQ offers. They could maybe release a similar product that would be a codeless product.

The initial setup was difficult. 

It would be nice to have it on the cloud, like ACCELQ. That way, we don't need to set up it ourselves and don't need hardware for that. That would also allow for many people at many subsidiaries or locations to work simultaneously with it.

I'd like the possibility of automatically checking the installed browser version and automatically downloading the Selenium driver that suits the installed browser. Otherwise, you have to download and set up it manually, and if you get a new browser version, you have to do it every time, and it's time-consuming.

We've been using the solution for one year. 

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. 

Of course, you need a lot of time to optimize your scripts so that they run stable.

This is not really scalable. 

If you consider load tests or multi-thread testing, you need very powerful hardware to start several browsers. That's why in this aspect, not very scalable if you run tests in parallel.

We just have two people leveraging the solution right now. They use it regularly, on a daily basis. 

There is a lot of documentation and general product knowledge online. We don't have direct support contact as it is an open-source solution. 

We did previously use Eggplant. It's not open-source. It's actually pretty expensive. 

One benefit of Eggplant was testing mobile apps. Also, you don't find so much information on Stack Overflow or on the internet about Eggplant; they have good support.

It was not very easy to set up. 

We needed to add a lot of plugins like TestNG and Maven. The whole configuration was not very easy. I am not sure if it is the Selenium setup or just the whole system setup.

The solution is open-source and free to use. 

I'm an end-user. 

The solution is okay, however, you need to use it together with the TestNG and with Maven and use different plugins that improve it.

I'd rate the solution nine out of ten.

Our team primarily uses Selenium for web testing. It is useful for functional and regression testing. Although I am now managing a team and do not use any tools myself, my team works with several tools, including Selenium, Appium, KrayMaster, the Google Search tool, Postman, and Katalon Studio.

Using Selenium helps save money as it is an open-source tool. However, writing the code can be difficult and requires skilled personnel.

Selenium is a valuable tool for web testing, and it integrates easily with frameworks like the Gauge framework, making it easier than others. It supports different programming languages, including Java and JavaScript.

The most significant issue with Selenium is its difficulty in adapting to changing locators, which can hinder testing. Additionally, writing code can be challenging, especially for beginners.

I have been working with Selenium for about seven years.

While deploying and using Selenium, integrating frameworks and maintaining backups separately are areas that require more manual handling.

There is no need to contact the technical support team directly as there are many resources available online. Many people share solutions to common problems, so issues can often be resolved independently.

Neutral

Some colleagues argue that Cypress or Playwright might be better than Selenium, but we continue to use Selenium with the Gauge Framework.

As an open-source tool, Selenium does not have direct costs, but coding can be money-intensive because it is challenging.

Cypress and Playwright were considered by some colleagues as alternatives.

I mentioned that solving the issue of adapting to changing locators would significantly improve Selenium, potentially increasing its rating. Additionally, one can utilize web portals and AI to assist with problems.

I would rate it a seven out of ten.