Selenium HQ Reviews

• Support for UI Automation
• Language support - since it supports Java and other programming languages it is easy to integrate with other systems
• Multiple browser support
• Selenium Grid supports the execution of test case in distributed way

• It's open-source, so there's no need to pay for a license
• Support different programming language hence DevOps and QA work together to built better test suite
• Since it is a lightweight tool, hence it helps in running test cases fast

There is no good tool to find the Xpath. They should provide a good tool to find Xpath for dynamic elements and integrate API (REST/ SOAP) testing support.

I've been using it for five years.

There were no issues with the deployment.

There have been no issues with the stability.

There have been no issues with the scalability.

I have used Silk Test and QTP before using Selenium. The reason for choosing the product can be found in answer 4 and 5.

I used SilkTest and QTP before using Selenium

It was easy to set-up.

We did it in-house one, you choose the solution which best suite your needs. Don’t spend to much time in building robust solution unless it is really required.

I have invested my time in learning the tool and got good recognition for creating automation framework. It can continue to run as open source tool.

You just need to choose the solution which best suites for you.

We have a lot of information that we are putting on different websites and social media platforms because we need to inform our social network users about what we are doing, what we are planning to do, and what was done. Sometimes, it's information which is the same, or it's the same on different websites, in different web software, and so on. I am using Selenium mostly for this purpose.

I like its simplicity.

It would be better if it accommodated non-techy end-users. I think it's still a product for developers. That's why it's not common for end-users, and especially for RPA activities or tasks. It's hard to automate tasks for end-users. If it will be easier, more user-friendly, and so on, perhaps it can be more interesting for this kind of user. 

The second thing, when you are working in IT, you know about such tools. But if you are on the business side, you don't have much information at all.

I would like to see easy onboarding with training for end-users. Because there is a lot of stuff for developers, but for end-users, I would say none or approximately none.

I've been using Selenium HQ for five years.

I didn't have problems with stability.

I didn't have problems with scalability.

The initial setup is complex. I think some changes were done, but it's still too complicated for end-users. 

I would advise potential users to contact their IT guys because they will have a problem setting up the first automation. Of course, if there are people like me who want to develop their own knowledge, I would say they need time to get to know how to use it, optimize the process, etc. 

But if not, it will be easier for end-users to start with some kind of RPA offering by different vendors because they have their tools prepared for the end-users, for onboarding, and so on.
Because these open-source tools are still tools made for developers and IT guys, not for end-user.

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

We use the solution for the test automation of web solutions. It also helps us to create web browsers.  

My company uses the solution for critical deployments. 

I am impressed with the product's ability to catch content from website. 

I have found that at times the tool does not catch the class features of website content correctly. The product's AWS configuration is also hard. 

I have been using the tool for five years. 

The tool is stable but needs to update to the new version of Chrome. 

I would rate the product's scalability an eight out of ten. My company has 2000 users for the solution.

I have never used support. I would search on the internet for tutorials. 

The solution's setup is easy in the local environment but complex on the server side. You need to also update the Chrome version in the cloud before setting it up in the local environment. 

I would rate the product an eight out of ten. The product is easy to use. 

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.

We are using mobile application and functional testing. It performs pretty well. 

We are using Selenium for scripting. We use Sauce Labs for the hardware device coverage on the client side.

The primary benefit is its cost and the ability to use the cloud. 

We use it with Sauce Labs. So, we have a large base of real devices and emulators, as well as breadth of coverage.

• Flexibility
• Scalability

It does require a programming skill set. I would like the product not to require a heavy programming skill set and be more user-friendly for someone without a programming background.

So far, I have not have any issues with its stability.

Technical support is one of the downsides of it. When you are buying a commercial tool from a vendor, your technical support is readily available but you are paying for it. However, they're going to take care of you. When you're dealing with open source, your support is based on research that you can do on the Internet. You rely on somebody else having had the same experience or one of the developers of the code having put something out there on the subject.

This product is open source and free. That was a huge deciding factor for us getting into it.

I don’t see it as a company spending money on anything. I like to keep up with the market because I built my career around test automation.

Most important criteria when selecting a vendor: 

• Ease of implementation
• Ease of adaptability
• How much skill set would be required to operate it. Can I take somebody with no programming background and get them up and running on it, or does it require a heavy-duty programming background?

FitNesse: The ability to present your tests on a wiki page and hooking them up to the scripts/fixtures. This is an amazing feature as you could literally ask your product owner, business analysts/developers to go to wiki and see all tests that are written and running automatically. Using the Gherkin format this can be very user readable, and one can also run those tests from the wiki themselves. They can even write their own tests using the available functions. Can easily be connected to Jenkins as well.

Selenium: The part with Selenium I like the most is the ability to parse and select an element from DOM. The various selectors make the job easier! At the same time one has to be careful of the selectors one uses, as it can make performance inefficient. With Selenium, one has a lot of freedom to choose the rest of the tools needed to make a full-fledged automation framework. You can use Cucumber/testing/JUnit as your test engine. You can use something else for reporting, etc., etc. It's available in so many languages, so you can choose the one which is close to your application. It’s not like a separate tool with its own scripting framework lying and maintained on the side. If your application is in Java, you can also choose Java for Selenium. If its C#, you can choose C# for Selenium. So your developers can also contribute to your framework and code.

It has largely improved our efficiency in QA. So every regression we don’t have to run a lot of repeatable test cases for which the flow didn’t change. However they are important to execute, so automation helps us there. Daily Smoke runs and weekly regression runs ensure that Build is continuously tested, which helps in Continuous Integration and Continuous Delivery. I must be cautious here: You cannot automate everything as you still need the exploratory and cognitive behavior of a human being. So a part of testing over releases will still be manual. Efficiency can be achieved on repeatable tasks, which is still quite a gain.

Selenium could offer better ways to record and create scripts. IDE is available, however, it can be improved.

About four years.

No issues with stability. The Selenium community maintains it well.

Depends on the hardware we choose to host the automation scripts. No issues there.

There is enough material on the internet and the community answers questions/problems pretty fast. So, very good!

In the past I have used HPE QuickTest Pro, now ALM. Also Coded UI. However, Selenium is better for web applications, although the others provide more versatility in terms of supporting more than just web applications! They come with their license fees as well.

As Selenium is just a library, you have to build the whole framework around it yourself. There are enough templates available on internet to give you a head start, though.

There is no pricing cost. License is Apache License 2.0.

Ours is a web application and, considering my experience with other tools, our choice was easier. We did try Protractor and Jasmine, however Protractor is also based on Selenium. It works better with angular pages. For us, Selenium was enough and we want to use FitNesse.

If you have a web application, I would strongly recommend this, as it has a lot of benefits as described above.

The main use case of Selenium HQ is for end-to-end automation of UI applications.

Selenium HQ's most valuable feature is picking up and entering values from web pages.

An improvement to Selenium HQ would be the inclusion of a facility to work on Shadow DOM. I would also like better integration with applications like Salesforce.

I've worked with Selenium HQ for eight to nine years.

Selenium HQ is stable.

Selenium HQ is scalable - you can execute on multiple browsers in parallel.

Previously, I used UFT but switched to Selenium HQ as it's an open-source product while UFT is licensed.

The initial setup was straightforward, and deployment took five months.

We used an in-house team.

In order to use Selenium HQ comfortably, you need to be very strong on Java skills. I would give Selenium HQ a rating of seven out of ten.

Our primary use case is we have a new development going on for our tool, our project, where we have to test web-based applications. These are all web-based applications wherein Selenium fits well for all the web applications.

I have found using IDE and Cucumber framework is good.

I would like to see some reporting or test management tools.

I have been working with Selenium HQ for the past eight months.

The stability is evident and it is a good tool.

The scalability is good. On a scale of one to ten, I would rate it a nine.

When it comes to technical support you do have to go online for the support community.

Selenium only works with web-based applications, it does not work on desktops, or any Java-based, form-based applications. There is no automation for any of these kinds of applications. With the Oracle Application Testing Suite, it can do anything. Currently, it has some drawbacks in automating desktop-based applications. However, the main difference is Selenium only sticks to web-based applications. But Oracle Application Testing Suite, or any other testing suite, like UFT, can automate a form-based or desktop-based application.

The initial setup is very simple and not complex.

The pricing is open source.

If you are wanting to do some web-based automation, definitely Selenium HQ is a good solution. I would rate Selenium HQ a six out of ten.