When we execute our smoke test, we're able to perform them really quickly with Selenium. Currently, in our project, we have 12 smoke tests. If I have to run them sequentially, it is going to take half an hour. If I run them in parallel, each one of them takes less than two and a half minutes. So, I could do smoke tests in under three minutes and get feedback right away about whether everything is up and running. We do production deployments throughout the week, but we try to do our main deployments on Sunday. Sunday is not the best working day, but because it is a weekend, we can get our work done. We want to be able to perform these tests quickly. The same is applicable to our pre-prod environment. We can run our smoke test right away, and it will be able to tell us that all the dependencies for our applications are up and running. As compared to doing it manually, which can take a few hours, it is really quick. 

It saves time for regression testing. It takes about three people to do the regression testing manually for probably two or three hours, whereas you can do it a lot quicker if you can get them in parallel. So, you can get quick feedback about whether your application is up and running right away. You don't want to go down the road where you find a problem after four or five hours. You want to find it out as quickly as possible.

The solution has improved the company by reducing a lot of manual work.

The solution helps us improve and maintain a specific set of work quality. Also, it saves a lot of time for us.

The main improvement is the lower cost of regression tests. It will probably be more expensive in the first iteration (more or less 30%), however, we can save up to 40% or 50% in the next runs. 

Another benefit is that, once the test scripts have been built, it is not necessary for the person executing the test processes to be an expert, allowing resources and costs to be optimized with lower costs in human talent. 

In addition, the barrier of functional knowledge is eliminated; specialization is not necessary during the life cycle of the tests.

My customer previously validated every file and it would take almost 15-20 minutes for a document. They used to randomly select and test only 100 out of the thousands, maybe 85,000, files, to pick up sampling. Each file would take around 20 to 25 minutes, so we were not able to do it manually, but with the help of Selenium, we were able to test all the files in two days. It saves a lot of time.

We are saving time with regression testing by using test automation.  

Selenium is also open source, so now we are integrating all our automation tests into the full pipeline. 

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.

My company uses the solution for critical deployments. 

Selenium HQ has helped us through its automation capabilities, because testing manually takes a lot of time and money. For instance, we have now automated an end-to-end application for the test cases. So now it's really easy for the testers, and it reduces the time and effort taken to do their work.

There are many phases that must be completed while delivering the product to the client, and in the system integration testing phase we can easily execute our automation and scripts, which saves us a lot of time and enhances the testing process dramatically.

We provide IT services and solutions, and this solution helped our clients reduce their manual testing efforts to greater level. Our clients have realized benefits by reducing their testing cycle from three days to three hours through Selenium.

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. 

• 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

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.

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.

We are a testing company. We can automate testing using Selenium.

Reduces Manpower, Testing is become much faster which is helpful for faster Project delivery. 

Selenium has improved the way we work because if you do what we need to do manually, you'll have to expend a lot of time. For example, it would be a huge chore to navigate through an application manually every day, and particularly if there's a new build on the way, you would have to check all the regulations over again by hand. That would simply take too much time, and so what Selenium does for us is that in one resource it can handle the work of three, four resources, provided that the scripts are straightforward and coded properly. That's the main cool thing about Selenium, I would say.

We work in the healthcare domain.

If for example, I get a diagnosis for a particular patient, it continuously changes as there are at least 100 sets of data. It's impossible to make that work for each and every build manually. The parameterization and parallelization have helped us with the inputting. 

Every week we have reviews. We have automated the stabilized areas. It has helped us to add speed to our cycles.

This has improved our organization through the automation of UI test cases.

Reduced license cost

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.

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

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

Selenium Webdriver has streamlined the entire quality assurance process in our organization. As the regression suites run more frequently than before bugs are reported to developers at a faster rate which has in turn helped in attaining a rapid stability of the product. Alongside these automation scripts can be used to validate the functionality across various browsers and platforms which reduces time and effort considerably.

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.

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 run automated test cases after every deployment. The product helped us to implement continuous integration and worry free deployment process.

Automation testing improves the quality we deliver and reduce the time for regression testing.

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.

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.

Nowadays we are using the solution to allow old solutions to run through it. This way, we don't need to go check functionalities created previously. We just run the automation. In just one click you run the automations through. It saves a lot of time and allows us to focus on other things.

I’ve used Selenium in multiple ways of the years. In one case I was working on a web site that got updated once a week. Mostly by others. Every week we would find out that a page changed that we were not expecting because we had changed included content, not knowing it was appearing on another page. I convinced management to allow me to write a script that went to each page on the production site and compare the page to the stage site. I reported the changes to management so that if they didn’t know about them, they were aware of the change.

On another site, we used Selenium to do basic application level testing. Just about the time I would start to think I was wasting my time, the test would reveal a problem that needed to be addressed.

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.

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.

It is an awesome tool to use with great ROI, we have been using this tool extensively in most of our projects to reduce the manual regression efforts and to prevent production defects. Another beauty of this tool is to extend and integrate with other functional & non functional tools(Jmeter, OWASP ZAP, Appium ..etc.)

Recently we have implemented the Extended Reporting to support rich reporting structure with Charts,Dashboards that would be easy for stakeholders to Analyze and arrive at decisions. 

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

Selenuim helps us during testing. We are able to reduce the number and frequency of manual efforts by using scripts.

We designed the Omani-channel automation framework, and achieved the maximum testing coverage includes localization (approximately 19), environment (web and mobile [iOS and Android]), and browser.

Cost effective solution for automation test.

Selenium is an automation tool which allows to perform automation web testing and reduce amount of manual tests.

I can run a set of regression test cases with every release to QA.

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.

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.

Selenium has two uses in my company. Firstly, our QA team uses Selenium to automate their tests. Secondly, our product BrowserStack Automate is based over Selenium and lets you run any Selenium script on different browser and OS combinations.

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.

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)

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

It allowed us to be assured that basic functionality works fine and to be informed about bugs quickly.

We are using this product to do regression testing. In this way it has improved the quality of our product.

Selenium is now being implemented for testing in many browsers, e.g. IE, Firefox, Chrome, Safari, Opera, Edge, etc. Also, we have implemented it in many other features in form of a framework.