Selenium HQ Reviews

Some valuable features are that it is easy to use and the ability to use forums for any issues that arise.

Regression testing time was greatly reduced, following implementation of Selenium automated test suites.

Sometimes, without codes or tests being altered, errors would result. This was often due to the speed at which the test was run. Therefore, I would say robustness is an area for improvement.

I have used this product for five years.

This product is easy to deploy.

I did encounter some stability issues. So, I found it was better to run automation scripts at slower speeds to get consistent results.

I have not encountered any scalability issues.

I did not contact customer service.

The beauty of Selenium is that since many people use it, technical questions can be quickly answered in many available online forums.

I have not used any other solution before.

The setup was a straightforward process. It was easy to download the latest version from the website.

We implemented this product in-house.

Regression testing could be completed within hours at the end of each sprint, rather than taking days of manual testing.

This is an open source, so this product was free.

We have not evaluated any other options.

If you are testing websites, this is a great tool. It is easy to use, even without much coding knowledge. Testers do not need to be very technical to start creating useful test cases.

It's free and continuously improved e.g. support for mobile, and new browsers. Also special services allow remote cross-browser testing on desktop and mobile browser (such as BrowserStack or SauceLabs).

Also the automation of Microsoft Edge is supported, where as other tools are having issues.

Regression tests for multiple browsers are now automated robustly across all main browsers.

• Video controls of an embedded HTML5 video
• AJAX/web 2.0 dynamic web content (though there is a framework called Protractor for Angular)
• Better detection if a page has indeed finished loading

I've used it for three years.

Never

Due to its high rate in releases sometimes working code cannot be executed after an upgrade due to a new feature or different behaviour.

Service is only available through a community (LinkedIn, Stackoverflow) but since this product is widely used you can always find a solution to your problem.

It was very straightforward, just one line of code, with two dependencies and you already have a browser up and running ready to be automated.

I made the concept and implementation myself.

No license necessary, but to get the best results it requires a Java Software Developer with WebDev-background and a tester attitude. Tests can be automated fairly quickly and across the main browsers therefore you can get results in less than a week.

Don’t forget the maintenance that is required to keep the framework running, therefore I would suggest the Page-Object-Model, to separate the test logic from the test object. Also you might wanna start on Chrome, it’s better supported.

Ranorex, Sahi, TestComplete, TestWhizz, QF-Test, WatiR, Squish, CodedUI

Selenium is an open source automation tool founded in 2004 by Jason Huggins used widely for functional testing of web based applications. It supports multiple languages and browsers which gives it the versatility. Users can develop their automation framework in the language of their choice and test their product across various browsers. The most vital feature of Selenium Webdriver is, that it allows report generation with the help of TestNG.

Selenium Webdriver has streamlined the entire quality assurance process in our organization. As the regression suites run more frequently than before bugs are reported to developers at a faster rate which has in turn helped in attaining a rapid stability of the product. Alongside these automation scripts can be used to validate the functionality across various browsers and platforms which reduces time and effort considerably.

In the future releases I would like to see a support for testing images in web applications and a provision for identifying captcha.

There were no issues with deployment.

There were no issues with the stability.

There are no issues with its scalability.

Implementing an automation tool for Quality assurance has become the latest trend in many organisations.

1. The biggest challenge is to identify whether there is really a need for an automation tool. Incorporating automation requires a robust product which undergoes minimal changes during its lifetime otherwise the automation scripts would require constant change.
2. Selenium only supports web based applications and it is not suitable for testing small sized products which can be easily tested manually. The effort in incorporating an automation framework would be larger than testing it manually.
3. User should have good knowledge of any of the programming languages supported like Java, C#, Ruby / Python to build an automation framework.
4. Building an automation framework can be used easily across team with minimal training.

• Selenium WebDriver can be used only for web test automation.
• The framework is very flexible and powerful.
• It can be used together with other frameworks for unit testing (JUNIT, TestNG), reporting (Allure), screenshot (aShot).
• It can be used for creating automation scripts and execute them locally, in a locally managed computer grid or in the cloud.
• It is great that Selenium works on any operating system and with many programming languages.

One thing that brings a lot of benefits is automating the smoke tests executed for each new build. If the automated tests are then integrated using Jenkins in the process of generating new builds, this leads to having better application builds.

I don't have any suggestions for the time being, but because it's open source, the only support is from forums and non-vendor resources.

I've used it for three years.

No issues encountered.

No issues encountered.

No issues encountered.

Being an open source product, there is no customer service or technical support available.

I used QTP previously for web test automation. Until recently, QTP had limitations because of the scripting language (VB Script) and inability to run automation scripts on multiple operating systems and browsers. After starting work with Selenium, I did not consider any other automation tool for web automation.

The set up was fairly easy. I started creating scripts and running them on my local computer. In time, as soon as the script number went up, I started running them in the cloud.

I did it in-house. Start small and make gradual changes when implementing Selenium WebDriver.

The product is fantastic. It requires development knowledge so if you want to get most of it, learn a programming language well first.

• Open source
• Ability to run tests across multiple browsers and OS
• Using Java as programming language

1. There are important projects in my organization which require a lot of cross browser testing to make sure that the application functions across different types of browsers eg. Internet Explorer, Chrome, FireFox, and Safari along with different versions eg IE9,10,11 etc. Hence we needed a tool which can run our tests across all these browsers in different machines to ensure defect free application. We have been able to fix many browser related issues in the application before deployment. Thus our efficiency of delivering a higher quality product has been increased a lot.
   This is important because our end users may use any kind of browser to use the application and we don’t want to get into issues where our applications crashes in 1 browser and works well in other.
   
2. A lot of time & cost has been saved by using Selenium automation because now we don’t need all browsers to be tested by manual testers. Just 1 automation script is required which can be run across different browsers. We only need 1 person to kick off the script execution

We have seen latency issues with Internet Explorer. I would like to see better support for Internet Explorer.

I've used it for one year and one month.

I've seen latency issues in IE while executing scripts. The same script runs faster in Chrome and FireFox. Sometimes, the same xpath may not identify an object in Internet Explorer, but will identify it in Chrome/FireFox. So we have to write a different code in that case. This is not a very common scenario though.

Although there is no customer service for this, the code documentation and online resources make it easy to work with.

We used IBM Rational Functional Tester v8.5. The reason we switched over this product was because Selenium WebDriver:

• Is Open source
• Supports execution in multiple browsers
• Has the ability to run multiple tests across browsers and OS at the same time using Selenium Grid

It was straightforward. All we needed was an editor like Eclipse and all the required JAR files and driver executables. All these are available online.

We did it in-house. You should have JRE up to date, and make sure your IDE is configured properly. All driver executables should be downloaded and all JAR files should be applied to the project.

We have saved overs 400 hours of effort in our regression testing.

There is no license cost.

We use Selenium HQ for automation and API integration.

The most valuable features of Selenium HQ are it is open-source, has a good interface, and integrates well.

I have been using Selenium HQ for approximately four years.

Selenium has been giving us failures sometimes. It is not working one hundred percent of the time when we are creating elements. They need to improve the stability of the solution.

The solution takes a lot of time for the developers. For example, if we are trying to implement UiPath or Automation Anywhere the people who are non-technical can use these two solutions. Selenium HQ is not easy for someone that is new to use, it takes too long for developers to learn the solution. There are other solutions that do not require such a learning curve.

We have approximately 870 users using this solution.

Selenium HQ has a large online community where you can get help on any issues or problems.

The installation is straightforward.

I have evaluated other solutions.

If you have developers that can operate Selenium HQ then this solution will be a good fit. However, if your developers are new to Selenium it might be better to choose another solution.

I rate Selenium HQ an eight out of ten.

Selenium HQ is used by our organization to automate test scripts for our applications as well as to automate or regression tests carried out during software development.

The grids, as well as the selectors, are the most valuable features.

The ease of use for the whole tool.

I would like more usability and ease of use.

The graphical interface could be improved. It would be very helpful to be able to write scripts in a GUI, rather than depend so heavily on the command line.

I have been using Selenium HQ in my department for three years.

Selenium HQ is a stable product.

It is easy to scale Selenium HQ.

We have five members in our Quality Assurance team, and three are dedicated to Selenium.

We have plans to increase our usage in Selenium but the issue is time.

We have not contacted technical support. In a Google search, you can find the help you need. It's an open community.

We worked with other solutions previously and changed to Selenium because of the cost of the license.

We are also using Microsoft Team Foundation (TFS), which is now known as Azure DevOps. We are upgrading to DevOps.

The initial setup is straightforward.

It took half a day to deploy.

One person is enough to maintain this solution.

We completed the installation and deployment internally.

The cost of the license is better than other solutions. Selenium is a free tool. It's open-source.

To date, we have not paid any additional fees.

I would recommend using Selenium with Python, it will be helpful.

I would rate Selenium HQ a seven out of ten.

In my company, I use the tool for testing web browsers.

We basically use the product for two things. The first is for testing for a website. The other thing is for repeating actions so that you can repeat the same action over and over with ease and without having to repeat the original steps. 

The solution is free to use. It's open-source, and you can modify the source. 

You can use it on different platforms, including Windows, Linux, or macOS.

It's easy to find and receive help from other developers. There is a good community that surrounds it.

The solution has been very stable so far.

Sometimes it's difficult to understand the solution. It's a good solution, however, it has many specific things you need to know, or you need to learn about. For people that don't know about technology, maybe it's difficult to use. You have to know how to program. You need to be a developer.

The tool has two steps: first, when you record, and second when you play back. However, in the middle, you need to look at a file. You need to save a file and after that look at them. It would be ideal if the solution allowed for the process to be one step and more automatic. 

The initial setup is quite complex.

I've been using the solution for maybe two years or so at this point. It's been a while.

The stability of the solution is good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

I've never tried to scale the solution, however, it's my understanding that it is possible. On a scale from one to ten, I'd rate the potential to scale at a six or seven.

The tool is open source. Typically, when something is a commercial solution, there is more of a possibility of being scalable. We depend on other developers to grow the tool. 

Last year, we only had two people on the tool. However, this year, I want to grow that number to about ten. They are all engineers. Of the team, 80% would be quality engineers and 20% would be developers.

I don't use Selenium technical support. As an open-source tool, you need to go to the community and the forums.

Typically, you can find your answers pretty quickly. You can ask the community as well, and usually, someone gets back to you pretty fast.

I also use SmartBear. Selenium only works for web browsers, and sometimes I need to check an application. When that is the case, I cannot use Selenium, and I instead use SmartBear.

The initial setup is not straightforward. It's pretty complex.

It's complex due to the fact that you need to download a complement for the web browser and you need to recall the tests and you have to load the files. When you do a recall, the tools create a file with the steps. Before you need to playback, you need to load the file. It's not easy. You need to know some things about the tool. 

The deployment took maybe six months to possibly 10 months.

You only need one person for deployment and maintenance.

The solution is open-source and free to use. There are no licensing costs.

We did look at Katalon Studio before ultimately choosing Selenium HQ.

The principle difference is Katalon is one solution. You can't change the functionalities in the solution. It's also complex to use and demands a lot of memory. You need a lot of RAM or a big processor. It just takes up too many resources. 

We are just a customer and end-user.

I'm not sure which version number we're using. However, it is a version from 2020, from the last year or so.

I'd advise those considering the solution, if you want use SeleniumHQ, it's a good option if you have good developers that understand the tool and can make changes in the tool. If you have the right people on hand, it works very, very well.

I'd rate the solution at a seven out of ten. If it didn't need such technical expertise, I might rate it higher.