Selenium HQ Reviews

This is open-source product with large community, it allows to use your favourite language to write test framework.

Selenium is an automation tool which allows to perform automation web testing and reduce amount of manual tests.

Maybe more stable cross-browser autotesting (some times test which works ok for one browser fails in another).

I've used it for over four years.

There were no issues with the deployment.

Sometimes there are issues with automation testing in Internet Explorer.

There's no issues with the scalability.

This is open source product with large community, the main issues can be solved using this community

To use Selenium WebDriver effectively you should have good knowledge of programming language, this is one of the main complexity

Compared to commercial tools such as TestComplete, Selenium WebDriver is a better choice for web auto-testing. It allows us to write frameworks using object-oriented programming languages like Java.

To use Selenium WebDriver effectively user should have good knowledge of programming language, this is one of the main complexity. Using Selenium you have to write test framework using your favourite language and some additional tools should be used also (like Jenkins for CI and reports), this is the first step which should be done.

The ability to test on all of the major web browsers.

I’ve used Selenium in multiple ways of the years. In one case I was working on a web site that got updated once a week. Mostly by others. Every week we would find out that a page changed that we were not expecting because we had changed included content, not knowing it was appearing on another page. I convinced management to allow me to write a script that went to each page on the production site and compare the page to the stage site. I reported the changes to management so that if they didn’t know about them, they were aware of the change.

On another site, we used Selenium to do basic application level testing. Just about the time I would start to think I was wasting my time, the test would reveal a problem that needed to be addressed.

Can’t think of anything I would change.

I've used it for at least five years.

There's never been an issue with deploying it.

As the various browsers change, tests stop working. But that can hardly be blamed on Selenium. Every problem I've ever had has always been answered by “Get the most recent version of Selenium.”

I've never had a problem scaling the tests.

It is open source, I don’t think this applies. The documentation could use some work but there are books that fill this hole.

I had used TestComplete at one point a very long time ago. What I didn’t like about TC is that it was a complete development environment, which I didn’t really like. Selenium gives me the ability to write my test using the programming environment I am already familiar with.

The initial setup is pretty straightforward, but when you branch into using the Selenium Grid, things do get a bit more complex. It is all pretty easy now that I know how.

I implemented it myself using search engines and trial and error.

It’s free. And relatively easy to get setup.

Learn how to use the “Page Model” approach to creating tests. If you code direct to the Selenium API and don’t using the Page Model, as things change in your web application, it will become more and more difficult to update your test to reflect the changes.

I can easily integrate with TestNG and Maven. Also I am able to set servers and hubs to execute my test case against

I can run a set of regression test cases with every release to QA.

I would like to be able to capture HTML header information but I have not been able to do that yet

I've used it for three years.

There were no issues during deployment.

Currently WebDriver is having issues running against the latest of Firefox.

There have been no issues scaling it out.

There is none yet there is a lot sites where questions can answered.

I used Capybara. I am more familiar with Java

It was pretty straightforward. It needs some degree of programming knowledge.

We did it in-house.

It's free.

Go for it. This is one of the best open source solutions I know of.

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 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.

• 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.

It allows us to verify user flows effectively and very easily. I can use any web browser to assert user flows.

It's helped us get good coverage with functional regression tests, reducing the reduction of manual effort to sign off on every release. We can now do so in just one day to sign off a regression test as compared to 4 day before we had automated tests.

Plus, as the regression runs are invoked on every commit, the tool has also reduced the number of issues introduced by regressions and has highlighted the regression issues on every commit/push. This allows us to get very early fixes and reduces the risks associated with changes and releases.

Overall, there aren't any areas for improvement. However, there are some things you have to do make make effective use of the tool. Make sure the language you select to work with is the same as the language your applications is developed in. Also, make sure you use Selenium Grid to get the test and suites to run in parallel.

We've had no issues with deployment.

Stability has been fine for us.

It scales without issue.

It's open source, so there's no customer service.

It's customer service, so we provide our own technical support.

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.