Selenium Reviews

Test scripts for our customers are being executed in the backend which uses Selenium as a core framework.

We use Selenium primarily for testing the Web Applications that are being developed for the clients. It is mainly used by the QA department for writing automated scripts using Java and Javascript for testing various scenarios in the application. The QA team constantly keeps adding more test cases to the test suites to ensure maximum coverage and then combine it with Jenkins to run the test cases over night, so that we can get the test reports in the morning.

We're using Selenium WebDriver and Hub daily across the whole organization. We cover the most routine test cases on a daily basis to prevent any human-related errors. We get plenty of scheduled jobs to run tests overnight and get results quickly. Web GUI testing became easier for everyone on the team.

Selenium as an open source test platform/ framework is used by the whole organization. It is used as automation testing framework and widely used for UI testing.

We use Selenium daily in my organization. We started using it to run basic automation testing of our web forms. This helped us significantly cut down on the amount of time that it was taking to manually submit lead tests. This ended up leading to full automation of entire test suites.

Selenium is used by just our department which is quality assurance. We use it basically for the GUI regression testing. We have a virtual private branch exchange and a lot of telecom features available for the call centre workplace. The selenium tests help with automating and running the entire GUI checks each time a new feature is deployed. This is scheduled as a cron job that runs overnight and gets the results in a graphical format.

For one single department, we used Selenium software for our website application implementation. It was helpful in testing software infrastructure without a need to focus resources and time on learning new test scripting languages. We also utilized Selenium in assisting with the creation of automation that was carried out in test browsers. It was also beneficial for generating reports that we required.

Selenium was under review by my department when we were starting with automation. The main drive to use selenium was that it was free and it had a large community. It also supported many different languages and can be easily implemented with other software including Apache JMeter. It was also looked as a way to test API using scripting languages.

What made Selenium sound great was the compatibility with Firefox and other web browsers. It is a great tool for people who like to use playback and record and insert data using Excel or other programs. It's easy to upload and to use.

Selenium is an web automation tool, which was used by testers for automating web applications. Instead of doing regression testing manually, Selenium was used so that once script is coded, it can be used to run as many times as required. As Selenium was open source, it was easy and installing eclipse then including the Selenium jar files was an easier task.
The scripts can be executed in batch overnight / during weekends to ensure that application is working as per the requirements. Also, doing manual testing across multiple browsers, which is tedious & time consuming task, can be solved by using Selenium tools.

Selenium basically is being used for automation of an internal website by one of our clients, Huawei. It is a good open source tool, and since it is open source, it has replaced the legacy automation (paid) for better results.
We have coupled the Selenium framework with REST and use the test cases to automate the 564 test cases for the application which have been integrated to CI.
Since Infosys caters to hundreds of clients, [use by] the whole organization would be an over estimation in my view, but it is catching on throughout the organization to automate repetitive flows.

Selenium is used by the R&D department. It helps to ensure quality of maximum features in short duration when the product is being released at regular intervals.

It is used by our company to automate several web based products.

We used selenium to test our applications across the technology department. It helps test our products to ensure they do not contain bugs for our end users.

Selenium is used in my company for automated testing in web applications, and it allows us to avoid manual regression testing, and also allows us to fix regression bugs faster and more easily. It's fully integrated to CI, with a Selenium Grid being responsible to launch all browser drivers (allows Chrome, Firefox, IE/Edge, PhantomJS, etc...).

Our whole organization pretty much uses selenium to validate UI of web applications. It usually run on a daily and even several times a day basis. It executes the whole regression test suite whenever a new build is pushed.

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.

For us, Selenium is used solely by the QA department. Since a large majority of our projects include web design, we particularly use selenium for the assurance of our monotonous tasks. However monotonous they may be, as a vital part of our product - they need to be tested! Selenium helps facilitate the autonomous test cycles, and concurrently frees the hands of our department to handle much more engaging tasks.

Additionally, all companies (especially those in the field of marketing) face time constraints. As a lead currently managing a handful of very important projects, time is imperative; how can we maximize our time on things like stability, functionality, and engagement, while spending less human energy on small tasks like content and grammar checks? Well, if the application is web based - Selenium is one answer.

We use both Selenium IDE for quick-and-dirty automation tasks by non-technical users and the Java bindings to build out a robust suite of functional tests we can run for regression testing automatically. We also use the Python and Node bindings for similar tasks and automation efforts outside of testing, like deployment verification or monitoring of the site.

We use Selenium WebDriver for our online portal for effective test automation on a variety of use cases. Prior to writing this test automation QA would manually go through test cases manually with a "point & click" approach prior to every release/major feature which resulted in a large amount of time being spent on a simple process that was slowing our release cycle. With writing these test cases in Java using Selenium WebDriver tests they're able to be re-created with even more precision and tests cases quickly. The QA review process of a release went from a day or two to less than an hour.

It is used by most of the scrum team to automate web page testing. It's being used across the whole organization. It is used as UI automation tool. Scripts are written for smoke, sanity and regression testing purpose.

Selenium is widely used across all departments of an organization. It's primarily used for UI automation for mobile and desktop browsers.

First of all, let's point out that "Selenium" is a vague word. There are:

• "Selenium IDE" which is a simple plugin for Firefox, that has limited abilities to record and reply user actions along with using javascript snippets and parameterization.
• "WebDriver , AKA Selenium WD", is a package that can be as libraries to many programming languags such as Java, Ruby, Python and .net framework. Webdriver is way more powerful and flexible because you can use the programming language on your favor; For instance, you might want to use a database to read data as a data driven test, record results to another table, use Java robot to click on non-web elements or desktop windows, or even integrate Webdriver with headless browsers such as PhantomJS, that will help you to run the test in non-gui environments.
• Selenium Remote Control (RC) : This is a server-based selenium, being installed directly on web server and similar to WebDriver, can adopt various programming languages. In my opinion RC is getting obsolete and replaced with WebDriver except in special scenarios such as running multiple Webdriver Agents on client side as a Selenium Grid.

I love selenium because of its vast usefulness and capabilities. In many cases, it is totally compatible with expensive tools such as HP UFT or SmartBear TestComplete and let's not forget that Selenium is free and open source.

However, Selenium and WebDriver are not so strong on their own: They are weak on detecting Java applets and Flash elements and totally out of league when it comes to non-web elements. Fortunately, there are solutions to overcome such issues. For non-web elements, Java Robot or Python gtk is available. For modern Java applets that are based on swing elements, FEST is a useful tool to integrate with selenium to detect applet elements. Finally, Sikuli is an amazing library to locate elements based on their look (pixel by pixel), which is very useful to detect some Flash or Applet elements within GUI.

Selenium is used for web UI automation. We automate test cases for release regression runs. The whole organization uses it for Web testing. It provides feedback when developing new features and then running tests on old features to make sure nothing is broken. It gives us flexibility to run tests on different environments and browsers.

We are doing a design functional/UI data-driven automation testing framework using Selenium WebDriver(Java) and TestNG. We have several projects automated with selenium. They are all running reliably. This is a great way to manage the test data, it is especially good for multi-platform testing. Using Selenium, TestNG and Maven is a good set for designing the automation testing framework.