Selenium HQ Reviews

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.

FitNesse: The ability to present your tests on a wiki page and hooking them up to the scripts/fixtures. This is an amazing feature as you could literally ask your product owner, business analysts/developers to go to wiki and see all tests that are written and running automatically. Using the Gherkin format this can be very user readable, and one can also run those tests from the wiki themselves. They can even write their own tests using the available functions. Can easily be connected to Jenkins as well.

Selenium: The part with Selenium I like the most is the ability to parse and select an element from DOM. The various selectors make the job easier! At the same time one has to be careful of the selectors one uses, as it can make performance inefficient. With Selenium, one has a lot of freedom to choose the rest of the tools needed to make a full-fledged automation framework. You can use Cucumber/testing/JUnit as your test engine. You can use something else for reporting, etc., etc. It's available in so many languages, so you can choose the one which is close to your application. It’s not like a separate tool with its own scripting framework lying and maintained on the side. If your application is in Java, you can also choose Java for Selenium. If its C#, you can choose C# for Selenium. So your developers can also contribute to your framework and code.

It has largely improved our efficiency in QA. So every regression we don’t have to run a lot of repeatable test cases for which the flow didn’t change. However they are important to execute, so automation helps us there. Daily Smoke runs and weekly regression runs ensure that Build is continuously tested, which helps in Continuous Integration and Continuous Delivery. I must be cautious here: You cannot automate everything as you still need the exploratory and cognitive behavior of a human being. So a part of testing over releases will still be manual. Efficiency can be achieved on repeatable tasks, which is still quite a gain.

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

About four years.

No issues with stability. The Selenium community maintains it well.

Depends on the hardware we choose to host the automation scripts. No issues there.

There is enough material on the internet and the community answers questions/problems pretty fast. So, very good!

In the past I have used HPE QuickTest Pro, now ALM. Also Coded UI. However, Selenium is better for web applications, although the others provide more versatility in terms of supporting more than just web applications! They come with their license fees as well.

As Selenium is just a library, you have to build the whole framework around it yourself. There are enough templates available on internet to give you a head start, though.

There is no pricing cost. License is Apache License 2.0.

Ours is a web application and, considering my experience with other tools, our choice was easier. We did try Protractor and Jasmine, however Protractor is also based on Selenium. It works better with angular pages. For us, Selenium was enough and we want to use FitNesse.

If you have a web application, I would strongly recommend this, as it has a lot of benefits as described above.

Selenium WebDriver and Selenium IDE are useful.

Selenium IDE is able to record and playback. It was useful for me when I did not know coding. Selenium WebDriver has got packages which help in automating test cases.

The best part of Selenium WebDriver is that it supports multiple web browsers, thus, helping in cross-browser testing.

It is free to use and is not limited to any scripting language.

It has helped our organization as automating the test cases is much easier and faster now. It covers a wide range of test cases and in many browsers.

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

I have been using it for six months now.

There were some stability issues with Selenium. Sometimes my tests were not stable.

I have scalability issues with Selenium.

I did not use any technical support other than the help from my colleagues.

I have used Tricentis Tosca before, but I find Selenium much better as it is an open source tool and free to use.

The initial setup wasn't easy as I didn't know what packages to use and which ones were useful for my project.

Pricing: It is free to use.

I would advise others to use Selenium WebDriver and to understand all the packages useful for their project.

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

Automates more than 5000 test cases and takes around 30-36 hours by which it reduces the manual effort of one QA person in 20-25 days.

More than 2 Years

More than 2 Years.

Yes, with Internet Explorer only.

So far, No.

There are large forums available and their support staff were awesome.

Straightforward. But I would say the complexity will depend on the framework you create.

It's free!

Yes, Sahi Pro was on the list.

The tool supports most of the features you want to automate and the stability of the executions is good too. And finally, it's free!

Some valuable features are that it is easy to use and the ability to use forums for any issues that arise.

Regression testing time was greatly reduced, following implementation of Selenium automated test suites.

Sometimes, without codes or tests being altered, errors would result. This was often due to the speed at which the test was run. Therefore, I would say robustness is an area for improvement.

I have used this product for five years.

This product is easy to deploy.

I did encounter some stability issues. So, I found it was better to run automation scripts at slower speeds to get consistent results.

I have not encountered any scalability issues.

I did not contact customer service.

The beauty of Selenium is that since many people use it, technical questions can be quickly answered in many available online forums.

I have not used any other solution before.

The setup was a straightforward process. It was easy to download the latest version from the website.

We implemented this product in-house.

Regression testing could be completed within hours at the end of each sprint, rather than taking days of manual testing.

This is an open source, so this product was free.

We have not evaluated any other options.

If you are testing websites, this is a great tool. It is easy to use, even without much coding knowledge. Testers do not need to be very technical to start creating useful test cases.

It's free and continuously improved e.g. support for mobile, and new browsers. Also special services allow remote cross-browser testing on desktop and mobile browser (such as BrowserStack or SauceLabs).

Also the automation of Microsoft Edge is supported, where as other tools are having issues.

Regression tests for multiple browsers are now automated robustly across all main browsers.

• Video controls of an embedded HTML5 video
• AJAX/web 2.0 dynamic web content (though there is a framework called Protractor for Angular)
• Better detection if a page has indeed finished loading

I've used it for three years.

Never

Due to its high rate in releases sometimes working code cannot be executed after an upgrade due to a new feature or different behaviour.

Service is only available through a community (LinkedIn, Stackoverflow) but since this product is widely used you can always find a solution to your problem.

It was very straightforward, just one line of code, with two dependencies and you already have a browser up and running ready to be automated.

I made the concept and implementation myself.

No license necessary, but to get the best results it requires a Java Software Developer with WebDev-background and a tester attitude. Tests can be automated fairly quickly and across the main browsers therefore you can get results in less than a week.

Don’t forget the maintenance that is required to keep the framework running, therefore I would suggest the Page-Object-Model, to separate the test logic from the test object. Also you might wanna start on Chrome, it’s better supported.

Ranorex, Sahi, TestComplete, TestWhizz, QF-Test, WatiR, Squish, CodedUI