Selenium HQ Pros and Cons

The ability to present your tests on a wiki page and hooking them up to the scripts/fixtures.

It supports most of the mainstream browsers such as Chrome, Firefox, IE and etc.

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

Our platform runs into several thousand screens and a few thousand test cases, something which would typically take months to test manually. As of today, the entire process takes a little over two days to run.

Language support - since it supports Java and other programming languages it is easy to integrate with other systems.

Selenium WebDriver and Selenium IDE are useful.

Selenium web driver - Java.

It supports most of the actions that a user would do on a website.

Selenium has helped to complete tests in less time, which would not be possible relying on manual testing only.

It is programming language agnostic, you can write tests in most currently used languages.

It has helped to complete tests in less time, which would not be possible relying on manual testing only.

All the features in Selenium to automate the UI.

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

It is not easy to make IE plus Selenium work good as other browsers. Firefox and Chrome are the best ones to work with Selenium.

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.

In the beginning, we had issues with several test cases failing during regression. Over a period of time, we built our own framework around Selenium which helped us overcome of these issues.

Improvement in Selenium's ability to identify and wait for the page/element to load would be a big plus. This would ensure that our failed test cases will drop by 60%.

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.

Selenium has room for improvement as it does not support the tests and result-sharing in anything but a manual way.

Handling frames and windows needs to be improved.

There are stability issues with Internet Explorer only.

It would be very great if Selenium would provide some framework examples so newcomers could get started more quickly.

​To simplify the development process, everyone needs to do a Selenium Framework to acquire the web application functions and features from Selenium methods.

Selenium Grid set-up is bit complex.