Selenium HQ Reviews

We are using mobile application and functional testing. It performs pretty well. 

We are using Selenium for scripting. We use Sauce Labs for the hardware device coverage on the client side.

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

We use it with Sauce Labs. So, we have a large base of real devices and emulators, as well as breadth of coverage.

• Flexibility
• Scalability

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.

So far, I have not have any issues with its stability.

Technical support is one of the downsides of it. When you are buying a commercial tool from a vendor, your technical support is readily available but you are paying for it. However, they're going to take care of you. When you're dealing with open source, your support is based on research that you can do on the Internet. You rely on somebody else having had the same experience or one of the developers of the code having put something out there on the subject.

This product is open source and free. That was a huge deciding factor for us getting into it.

I don’t see it as a company spending money on anything. I like to keep up with the market because I built my career around test automation.

Most important criteria when selecting a vendor: 

• Ease of implementation
• Ease of adaptability
• How much skill set would be required to operate it. Can I take somebody with no programming background and get them up and running on it, or does it require a heavy-duty programming background?

We primarily have been using Selenium WebDriver for functional and regression testing of our business management platform. 

Our technology stack includes Apache HTTP, Tomcat, PostgreSQL, CentOS, Java, J2EE, JavaScript, and Eclipse. Plus, we are using Selenium WebDrivers and TestNG for testing with Firefox and Chrome. 

Our platform runs into several thousand screens and a few thousand test cases, something which would typically take months to test manually. However, we have been using Selenium to automate our testing process since day one. As of today, the entire process takes a little over two days to run. We plan to further optimize it and bring this duration down to about 12 hours.

We plan to integrate Selenium with JMeter for performance testing, too. 

WebDriver and Grid: Without these, we would have been nowhere so far. The shear size of team/software license required to accomplish this humongous task would have thrown us out of business. 

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%. Introduction of FluentWait has improved things, but it does not work in all scenarios 

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. 

I have had experience with Rational tools in the past, but with DWA Commerce, we wanted to go the open source route. 

We have had extensive experience in testing and have pretty much worked with most testing solutions. Therefore, we did not have to go in for a re-evaluation. Our choice was clear. 

Just go for it. 

I have used Selenium in many test automation projects from web report applications to internet banking.

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

Compatibility with all major browsers; it has become the industry standard.

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

• To simplify the development process, everyone needs to do a Selenium Framework to acquire the web application functions and features from Selenium methods.
• It would be very great if Selenium would provide some framework examples so newcomers could get started more quickly.

We took Selenium for web product test automation and as it very well suits as it has capacity to execute in different browser, different environment. Also it has lot other capacities to scale up test automation and yield better ROI.

Web-based application automation are mostly done using Selenium. It's the right automation tool as a replacement for manual regression testing that indispensably reduces the testing time due to its cross-browser, parallel, and remote executions.

- Most importantly, it is an open source tool.

- Parallel executions (same browser in parallel, different browser in parallel).

- Remote executions using Node and Hub.

- Integration with CI tools like Jenkins

- Multi-platform support (for details have a look at http://www.seleniumhq.org/about/platforms.jsp).

- Cross-browser Support (Chrome, Firefox, different versions of IE, Safari, Opera).

- Supported environments are Windows, Linux & Mac.

- Supports different scripting languages (JAVA, C#, Perl, PHP, Python, Ruby, Objective C, Javascript).

- Huge user community.

It has extensive support for Chrome and Firefox, but more is needed for IE, Edge and Safari.

To some extent it is unstable while executing against different versions of IE browser, but that could be overcome through some work-around and framework design. Edge browser executions are not stable as IE browsers.

Obviously, we have better support from various users as it is an open source tool. We have a huge number of customers in the open community at different levels to provide support.

Basically, to start with setup is straightforward and easier. If you use the remote web-driver, it is slightly complex to make the setup.

Our in-house team is used for the entire implementation of the framework. Being open-source, lot of valuable additions are made in a free-flow while developing the framework.

It's an open source tool.

We use it to make our UI functional tests, layout test, and any tests related to the browsers.

1. We have automation tests (API, UI, unit, integration tests, and etc.). It saves on our manual QA time.
2. It reduces our manual QA repeatable works.
3. It saves our manual QA's energy.
4. The QA time move from manual QA to automation QA, and improve the relationship between developer and QA, Since automation tests make them work closer.
5. QA becomes more technical and love to know more about technical and architecture of the code such as they have to use GitHub, CI system, servers, and etc.
6. QA know more about tests such as unit tests, integration tests, and Selenium UI tests.
7. Make QA life much fun/easier.
8. Deduce the developers work such as automation QA/developer develops the test library and test framework, both developer and QA, some times, PM also can develop their own tests by using the test library and test framework.

1. Selenium is a good tool to do UI testing
2. It works with many popular programming languages such as Java, JavaScript and etc.
3. It supports most of the mainstream browsers such as Chrome, Firefox, IE and etc.
4. It supports mobile local application as well and work with Appium.
5. It is free.
6. Selenium grid is a wonderful tool.
7. BrowserStack and Sauce Labs work with Selenium.
8. Headless browser, such as Xvfb and PhantomJS, can work with Selenium as well.
9. Selenium works with CI system such as TeamCity, Jenkins, and CircleCI.
10. Selenium can work with most programming languages. I use Java more as I am really comfortable using it.
11. I do not use Selenium IDE, but it can help the beginner to learn how to find the elements by XPath, CSS selector, and etc.
12. New geckodriver in new version of Selenium.
13. It is able to work with Galen test framework to do layout test.

1. Stability.
2. Documentation, the Java doc description for most of the API is almost empty. No example with no detail.
3. 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.
4. Java gets a lot of supports. Python as well. However, it seems not PHP. It is amazing, and Selenium can work with a lot of programming languages.
5. Firefox IDE tool needs to be improved.

Some times with timeout issues.

When your tests number increases, driver manager and Selenium Grid performance become important.

There are a lot of test frameworks that support Selenium.

Selenium web driver - Java.

As traditional load testing we use some expensive tools available in the market, but with the help of Selenium we started automating the browser and done load testing for light application.

Handling frames and windows needs to be improved.

I've been using it for one year.

No issues encountered.

No issues encountered.

No issues encountered.

9/10

Straightforward by using Selenium IDE.

We did an in-house implementation, doing our R&D over the internet.

Hot tool in market. Makes thing easier to use and implement. Demand increases cost.

Since it is an open source. It is free to use. However my company see it as the future of load testing.

You'll have a lot to do when automating many different applications. Just practice.

• Support for UI Automation
• Language support - since it supports Java and other programming languages it is easy to integrate with other systems
• Multiple browser support
• Selenium Grid supports the execution of test case in distributed way

• It's open-source, so there's no need to pay for a license
• Support different programming language hence DevOps and QA work together to built better test suite
• Since it is a lightweight tool, hence it helps in running test cases fast

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.

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

I have used Silk Test and QTP before using Selenium. The reason for choosing the product can be found in answer 4 and 5.

I used SilkTest and QTP before using Selenium

It was easy to set-up.

We did it in-house one, you choose the solution which best suite your needs. Don’t spend to much time in building robust solution unless it is really required.

I have invested my time in learning the tool and got good recognition for creating automation framework. It can continue to run as open source tool.

You just need to choose the solution which best suites for you.

All the features in Selenium to automate the UI.

Reduced license cost

I've used it for four years.

There were issues.

There were issues.

There were issues.

5/10

5/10

Selenium Grid set-up is bit complex.

I would advise you that it's a good tool to automate UI. There have been issues in the product.