Selenium HQ Reviews

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

When using Selenium WebDriver you will find that most valuable feature is integration with other technologies and frameworks.

Selenium can test almost any kind of web application and it supports many types of technologies. You can write scripts in various programming languages (Java, C#, Ruby, Python...).

Another important feature is scalable remote execution platform, you can execute your tests in parallel on great number of different machines using Selenium grid.

If used in right way (you can build your own test automation framework) it provides great test automation coverage and boosts time spent on writing automated test scripts. It can cope with almost any commercial tool in test automation area.

It would be nice to see more frequent releases and more bug fixes. Selenium has good support, but sometimes it seems that they mark some issues to easily with "won't fix" label.

Internet Explorer webdriver has some issues and should have better support.

I've been using it for one and half year, and intensely for the last eight months.

I encountered some smaller stability issues, but most of the time it can be solved quickly. There are also some minor issues with parallel test executions but there are workarounds for this specific cases so it can be avoided.

Support is pretty good, I would rate it 7/10.

I used a few commercial solutions in my career and Selenium offered me (almost) everything that this products did, in some cases even more. I chose it because it's open source, easy to integrate with other technologies/tools and offers everything that automation testing team needs.

Initial setup is complex just as any other development project setup is. Selenium has no installation files, it's just a bunch of libs which you need to import in your favorite IDE and set it up. It really depends on your experience, but no, it's not that complex.

It's an open source product, (probably) the most popular one in a whole software test automation industry. Although it's free and open source it has good support and great integration with different technologies.

If you have a good QA team with engineers which have strong technical background and experience in software development I would definitely recommend you Selenium WebDriver. It offers everything you need, you can make your own framework and architecture, based on your business and technical needs.

If you have non-technical QA team and you want test automation - Selenium WebDriver is not the right solution, you should invest in some commercial products which are easier to use and don't demand that level of technical skills from your team.

• Videos of test cases
• Scalable multi threading test execution

We are now able to execute 3000 test cases in less than one hour. This is a great milestone for us.

It needs more support for mobile devices and also on testing web services.

I've used it for four years.Videos of test cases + Scalable multi threading test execution.

We've had no issues with deployment.

We've had no issues with stability.

We've had no issues with scalability.

It's open source and therefore there is no customer support.

We used a different product that was not open source. We wanted to use open source.

It was not too complex, however, it would be complex for someone who doesn't know much about automation.

I implemented it through an in-house team. My advice would be to foresee all the problems that you might run in to in the future and design the framework based on that.

Make sure you get the set-up right initially.

It's open source, free, stable, and easy to use. It's the best solution on the market.

It's provided shorter testing cycles, and saves a lot of time and mental health for manual testers. It helps with performing scheduled builds, and automatically generated test reports, etc.

I'd like to be able to perform stability for tests on Internet Explorer.

We've used it for over one and a half years. We're running web test automation using Java language, and the Selenium library with the latest web drivers, alongside TestNG for managing test flow. We have Gradle for building and dependency management and Jenkins as CI tool. Tests are built and run on virtual machines (no remote driver).

The stability is a concern. Internet Explorer tests take three times longer to run and are a lot less stable than those run on Chrome, for example.

I haven't contacted them.

I haven't contacted them.

It took some time. I had to create, wrap and decorate a lot of its functionality.

It was done in-house.

We tried HP UFT, but did did not like the speed, and IDE. Also, there was no choice of programming language, it's not free, and a lot harder to maintain.

The library is nicely done. The webdriver communication with the browser is not perfect, though, especially IE. The longer the test is the higher the chance it will break down. It's impossible to reach 100% stability with more complicated tests. Very likely that the problem lies within Internet Explorer, not within the webdriver.

Very good for testers with programming experience and web developers, not so much for regular testers, unless they are given a “ready” framework and shown how to write tests.

• Open source
• Ability to run tests across multiple browsers and OS
• Using Java as programming language

1. There are important projects in my organization which require a lot of cross browser testing to make sure that the application functions across different types of browsers eg. Internet Explorer, Chrome, FireFox, and Safari along with different versions eg IE9,10,11 etc. Hence we needed a tool which can run our tests across all these browsers in different machines to ensure defect free application. We have been able to fix many browser related issues in the application before deployment. Thus our efficiency of delivering a higher quality product has been increased a lot.
   This is important because our end users may use any kind of browser to use the application and we don’t want to get into issues where our applications crashes in 1 browser and works well in other.
   
2. A lot of time & cost has been saved by using Selenium automation because now we don’t need all browsers to be tested by manual testers. Just 1 automation script is required which can be run across different browsers. We only need 1 person to kick off the script execution

We have seen latency issues with Internet Explorer. I would like to see better support for Internet Explorer.

I've used it for one year and one month.

I've seen latency issues in IE while executing scripts. The same script runs faster in Chrome and FireFox. Sometimes, the same xpath may not identify an object in Internet Explorer, but will identify it in Chrome/FireFox. So we have to write a different code in that case. This is not a very common scenario though.

Although there is no customer service for this, the code documentation and online resources make it easy to work with.

We used IBM Rational Functional Tester v8.5. The reason we switched over this product was because Selenium WebDriver:

• Is Open source
• Supports execution in multiple browsers
• Has the ability to run multiple tests across browsers and OS at the same time using Selenium Grid

It was straightforward. All we needed was an editor like Eclipse and all the required JAR files and driver executables. All these are available online.

We did it in-house. You should have JRE up to date, and make sure your IDE is configured properly. All driver executables should be downloaded and all JAR files should be applied to the project.

We have saved overs 400 hours of effort in our regression testing.

There is no license cost.

• Supports many scripting languages (Java, .NET, Php etc)
• Great functional testing tool with short learning curve, and this makes it easy for someone coming from programming background
• Supports multiple web browsers/OS
• Distributed (remote) testing

Selenium is not just a one tool. It has a collection of tools.Selenium IDE can be used for creating the smoke tests quickly. Then export the test cases to your favorite programming language and run against different browsers. Once test cases are exported to the programming language the power of target language can be used to improve the tests further (e.g reporting , db connection etc)

Integrating test reporting with WebDriver directly

Support for major browsers directly.

If you don’t have a budget, go with Selenium because it has a huge community and the versions are constantly updated. Also, it supports latest browers most of the time, and major competitors are using it. It’s reliable and extendable. When it comes to performance testing, you can use the same code for both Selenium and JMeter.