Selenium HQ Reviews

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

They are working on a new product which gives you an opportunity to test your product with different browsers at the same time.

They pay version is expensive, and I found it difficulot to implement.

I used the free trial for 14 days.

There were no issues with the deployment.

There were no issues with the stability.

There were no issues with the scalability.

10/10

7/10

At the beginning, it was difficult to implement then it works.

The free option is very limited, but the pay version is expensive.

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

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.

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 system is SaaS, and we use it for web-based regression tests that are being done locally at an in-home office or in the company office.

What I like about Selenium HQ is that we wrote it ourselves. I think it's perfect. It's a framework that you can use to devise your own products, which is nice.

Selenium HQ could have better interaction with SAP products.

I've been using Selenium for about a year now.

Selenium's stability is good.

Scalability has not been a problem for us.

We haven't really needed support. We write our own code, so if anything goes wrong, we can fix it.

Phil Ward:
Well, we set it up ourselves, so we knew what we were doing. Basically, the installation is ava-based, so you have to write Java code to get it working.

I would rate Selenium HQ nine out of 10. If someone is thinking about adopting Selenium HQ, I would encourage them to use it. However, you do need to be reasonably proficient in Java, C#, or C++.

The solution has two primary uses: using a robot to navigate to and search for issues, and helping with some algorithms with Python.

The data collection and sorting is the solution's most valuable feature.

The API that Selenium gives you doesn't act well with browsers. This should be improved. Right now, it's not stable.

The stability of the solution is good.

The scalability of the solution is good.

Technical support isn't very good. Sometimes their recommendations were not very clear.

The initial setup is straightforward. Deployment took about seven months.

We worked with a consultant that assisted us with the implementation.

I'm using a free version of the solution currently.

We use the on-premises deployment model.

It's a mature product that has been on the market for ten years.

I'd rate the solution seven out of ten.