Selenium HQ Reviews

They are working on a new product which gives you an opportunity to test your product with different browsers at the same time.

They pay version is expensive, and I found it difficulot to implement.

I used the free trial for 14 days.

There were no issues with the deployment.

There were no issues with the stability.

There were no issues with the scalability.

10/10

7/10

At the beginning, it was difficult to implement then it works.

The free option is very limited, but the pay version is expensive.

The most important features of Selenium, in my opinion, are:

• Multiple finding options (by Xpath, CSS class, ID, etc.
• It is a multi-platform, so it can be used in different languages

It allowed us to be assured that basic functionality works fine and to be informed about bugs quickly.

I would like to see a better method handling. I mean methods/properties like Displayed, which should return false when there is no such element on the page instead NoSuchElementException, which has to be handled in my code – it should be provided with Selenium.

We've had no issues with deployment.

It's been stable so far.

We've scaled sufficiently with it.

Please remember it is just a tool and not everything can be automized.

The solution has two primary uses: using a robot to navigate to and search for issues, and helping with some algorithms with Python.

The data collection and sorting is the solution's most valuable feature.

The API that Selenium gives you doesn't act well with browsers. This should be improved. Right now, it's not stable.

The stability of the solution is good.

The scalability of the solution is good.

Technical support isn't very good. Sometimes their recommendations were not very clear.

The initial setup is straightforward. Deployment took about seven months.

We worked with a consultant that assisted us with the implementation.

I'm using a free version of the solution currently.

We use the on-premises deployment model.

It's a mature product that has been on the market for ten years.

I'd rate the solution seven out of ten.

The system is SaaS, and we use it for web-based regression tests that are being done locally at an in-home office or in the company office.

What I like about Selenium HQ is that we wrote it ourselves. I think it's perfect. It's a framework that you can use to devise your own products, which is nice.

Selenium HQ could have better interaction with SAP products.

I've been using Selenium for about a year now.

Selenium's stability is good.

Scalability has not been a problem for us.

We haven't really needed support. We write our own code, so if anything goes wrong, we can fix it.

Phil Ward:
Well, we set it up ourselves, so we knew what we were doing. Basically, the installation is ava-based, so you have to write Java code to get it working.

I would rate Selenium HQ nine out of 10. If someone is thinking about adopting Selenium HQ, I would encourage them to use it. However, you do need to be reasonably proficient in Java, C#, or C++.

The parallel batch execution as well as reporting feature in the tests are very valuable to me.

We are using this product to do regression testing. In this way it has improved the quality of our product.

As of now I can't see anything which needs to be improved but once I am through with Selenium, will let you know.

I've been using it for one year and two months.

I have not had any issues with the deployment.

I have not had any issues with the stability.

I have not had any issues with the scalability.

It's an open source tool. So the only support is Google for us.

This product is more user friendly than others. So this is the reason for choosing this product.

The set-up was straightforward.

The most valuable features I've found are:

• Cross browser support 
• Easy to use

Selenium is now being implemented for testing in many browsers, e.g. IE, Firefox, Chrome, Safari, Opera, Edge, etc. Also, we have implemented it in many other features in form of a framework.

I would suggest cross-browser support need to be improved, as all methods do not support when we change the browser.

A few features such as synchronization techniques, cross-browser coding, and customized reporting need to be implemented.