Selenium HQ Reviews

• Browser
• Language and environment compatible
• Opensource

We designed the Omani-channel automation framework, and achieved the maximum testing coverage includes localization (approximately 19), environment (web and mobile [iOS and Android]), and browser.

I would like to see an improvement in the iOS automation for hybrid app's and try to comparable for desktop app automation.

I've used it for six years.

There were no issues with the deployment.

I observed like batch execution issues and comparability issues like AngularJS app's etc.

There were no issues with the scalability.

8/10 - they need to improve their in-office blog.

Used other is solutions for my assignments, and more opensource ones.

It's simple to set-up.

We did it in-house.

It's open-source so it's free.

You'll be good to go with this.

• Automate any web page by providing URL
• One can use any programming language such as Ruby, Java, Python and few others
• Support for several types of locators
• Cross browser support

We run automated test cases after every deployment. The product helped us to implement continuous integration and worry free deployment process.

I had issues testing a flash application with Selenium Webdriver.

I've used 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.

It is an open source product with a strong user base and lot of user community support.

I have briefly used QTP. There are a few reasons.It is an open-source tool and it has cross browser support. Testers can run automated test cases in different browser, and QA engineers can write test cases in his/her choice of language such as Java, Ruby, Python and a few others.

The set up is straightforward if you have a programming background.

It is an open source tool but price in terms of time it is totally worth it. It saves us lot of time and cost once implemented. The cross browser testing functionality helped us to find issues quicker in specific browsers.

The product has record and play back tool but it is always better to write your own code and implement the framework.

• Simple objects recognition
• It's easy to use
• Multi-language support
• Open source with good support
• A lot of information and help online

Selenium IDE needs to be improved not like just an record / play back tool, but as effective web elements spy. TestNG has more support, and also has ntegration with Appium and Jmeter which Selenium misses.

I've been using it for 10 years, since 2005.

Throughout the last five years, I have not had any difficulty to install or set-up Webdriver.

This is an open source, so some issues are always pop[ing up , but compared to other open source automation tools web driver is much much better.

It covers all regression testing with 20,000 test cases run during 24 hours and easy maintenance.

Customer support is very good for a non-commercial tool.

I used Silk Test and Win Runner previously. Borland SilkTest is an excellent tool, but it costs.

 It very straight forward and easy. Of course it’s required basic programming skills.

We have in house automation framework and it works great with continuous integration. I do not see reasons to pay for third party services.

It's a free tool.

Just use web driver and enjoy.

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.

• It supports many programming languages like Java, and Ruby etc.
• It can be plugged with Junit, TestNG and other Java frameworks for reporting
• CI can be achieved with tools like Jenkins

Cost effective solution for automation test.

Dynamic Debugging needs to be improved. Like QTP, there should be an option to run the test from a point or state of application. Currently the test should be run from the beginning to debug or test the new scenario which has been added.

I've used it for three years.

There were no issues with the deployment.

There are stability issues, especially when Mozilla Firefox updates.

There's no scalability issues.

It wasn't very difficult.

We did it in-house.

It's free and there's no licence needed.

An engineer from any background can learn and build automation easily.

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.

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.