We don't directly use Selenium. We have built a wrapper around Selenium so other teams can consume it.

We are using version 4.0.1. We run it on a Microsoft public cloud in the CI/CD server.

There are around four teams which are currently using this solution, and we have a target of having around 10 teams.

I've done headless execution and at times I've found that pretty useful.

I use Selenium HQ to migrate manual test cases in automation scripts. 

For example, with respect to a quality analyst, if I want to test a certain scenario, I have to write the test cases. It may be a small test case, a regulation test case, or a synergy test case. Selenium will migrate them in the automation script. Instead of executing all my test cases manually, I can run an automation suit that has been written with the help of Selenium. Selenium will execute this automation suit, and it will provide an execution report. The report will be 100% accurate using the code we wrote.

We basically use Selenium for smoke testing and regression testing. We don't use it much for functional testing because you can easily and manually use a bunch of tests and make them a Zephyr. We use Zephyr as our test case management tool, which is a kind of a plugin for JIRA. So, we create our test cases in Zephyr, and then they are tagged to be automated. After that, we put them into our regression suite. Each team has its own independent regression suite. Currently, my team has a couple hundred, but I know some teams have 500 or 600 in their suite. We also have a suite of smoke tests that we run through Selenium.

All the code is on-prem. We're currently just running the tests through the Jenkins pipeline, but we want to be able to run them in parallel in the cloud and a lot quicker. We are not quite there yet. 

We are using Selenium HQ for the automation of web applications.

The solution can be deployed on the cloud or on-premise.

The solution is for front-end testing. It is mainly a testing tool.

We use Selenium HQ for the web application we developed here.

The bank uses Selenium HQ for web application automation. We write functions in Java with the TestNG framework. Working with a reusable library, we develop classes for the login, homepage, and remaining components. Once you create everything for the web application, we run scripts in Jenkins overnight, and then come back to our framework if there are issues. Finally, we use Eclipse to debug the code.

We do UI-based functional testing in Selenium. We have prioritized some of the use cases that are most likely to be affected, and we have added those to our regression suite. Each week or each month, we trigger the regression suite to check that nothing is broken.

We are using Selenium HQ for automated UI testing of web applications.

I'm currently working on automation testing using Selenium and Cucumber. 

I am using it with Java, not with as a standalone implementation. It's Selenium with Cucumber and with TestNG.

It's a dependency that I am using from SeleniumHQ. It's a couple of components.

We primarily use it for automation testing. 

We use the product for mobile and API testing purposes.

We use the solution to perform tests and robotic process automation.

We primarily use the solution for normal regression tests.

Depending upon the functionality, I use Selenium to prepare the scenarios I'm doing. I start by writing automation scripts in Java. From there, we execute the scripts if there are any changes in the product. Then we upgrade this overnight along with Jenkins to make sure our application is running as expected. They feature continuous deployment and continuous integration with the help of our teams, so our product will be applied to more users once it's adequately tested.

the primary use cases of this solution are UI regression testing and API automation testing.

I use Selenium HQ to create automated scripts for automated applications.

We use Selenium HQ for the automation of functional test cases.

We are using a framework for Selenium HQ, which is behavior-driven. We have some features, such as login features. We write in normal English and the steps are converted into programming. We have one more feature in step definition, which connects both the feature file and step definition. In step definition, we write the program.

We are using SeleniumHQ for automating the test scripts.

We mainly use HQ for UI automation and some of the main functions of test cases. We are customers of Selenium. 

I'm using Selenium for low-budget projects, small projects, and mostly medium projects. I don't use it for anything on a large scale because it has some limitations. I'm also restricted by the level of knowledge and technicality of the people I can find on the market.

The solution can be deployed on-premise or on a private cloud. We mostly do on-premise installations. We always use the latest version.

I have led regression testing projects involving CRM, employee registration, and eCommerce. In each of these test cases, we have used the automation tool which has brought us benefits in time savings, shortening schedules, or recovering lost time - all of this leading to money savings. 

It's very useful when there are constant changes in the back-end. If the changes are constant in the source end it is not a good idea to use it. It is very important to previously evaluate the use of the tool depending on the characteristics.

We are using Selenium for web test automation.

We have a lot of information that we are putting on different websites and social media platforms because we need to inform our social network users about what we are doing, what we are planning to do, and what was done. Sometimes, it's information which is the same, or it's the same on different websites, in different web software, and so on. I am using Selenium mostly for this purpose.

We use the solution for the test automation of web solutions. It also helps us to create web browsers.  

The primary use case is web automation.

It has an extension available called Appiam that we use for our mobile automation.

We employ the version of the solution with the most ease of use, based on a search we conducted five or six years back. We now have a new client who likes the approach we used with a different one. We have a script to download the latest version, integrate it with the regression suite and then run it. Our current and previous clients equally approve of this approach. We make certain to utilize the latest version even when conducting tests during the development stage, as we find it easy to work with.

In my current project, we are working with an online pharmacy system, and for this system we maintain prescription details for patients. For example, patient names and other details such as where the patients live, what medications they need, and other types of information for various scenarios.

Then there is information for the doctors, such as what prescriptions there are in the system, and from which doctors they have been prescribed. These are the types of scenarios and test cases that we are automating with Selenium.

Specifically, I have been using Eggplant Functional and the Java Selenium pack, and Selenium WebDriver is the driver we use for developing the automation and scripts for the different test cases we use. This is our main testing tool for the online pharmacy system project and it is deployed on the cloud on a virtual machine because we are working from home now.

SeleniumHQ is WebDriver-related. It is a package that we can use with any language such as Java or Python.

We use Selenium for automation purposes. For example, if we need data from a website, we write code that will extract the data automatically. If there are logins or pop-ups, the code will close them, so we can extract the data. 

When we are testing a website, we use SeleniumHQ automation testing to determine if there are any bugs.  

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. 

We primarily use the solution for browser compatibility testing and web-based applications.

Our primary use case is for testing projects. We are a small startup company and each project has been assigned to test the web applications, elements, and identify the locators.

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 main use case of Selenium HQ is for end-to-end automation of UI applications.

My company started using Selenium HQ two years ago for unit testing. We were trying to evaluate the record and playback features. We are basically outsourcing this function, and we're charged for every developed feature and testing. So, we thought that we could test it ourselves using the record and playback feature. We were navigating our web application records in a macro and tried to reproduce that later. But for some reason, it's not the best solution for us.

Our primary use case is we have a new development going on for our tool, our project, where we have to test web-based applications. These are all web-based applications wherein Selenium fits well for all the web applications.

The primary use case for us is IntelliJ and IDEA.

I mainly use Selenium HQ for web application automation.

We primarily use the solution for automating a solution on the web and automating testing.

We primarily use the solution as a functional testing tool.

We use it when you have a large number of scenarios to be tested manually, you would go for a web-based automation solution.

I mainly use Selenium for web applications.

I'm the company's managing director and we are customers of Selenium. 

We are using selenium in our organization for Unit Testing, Smoke Testing, Sanity Testing and Regression Testing.

Currently I am doing mobile application automation with Appium and Selenium, as well as front-end application automation with tools like WAVE for mobile and desktop applications. The only area that I'm not involved in at present is API testing, though I am hoping there will be opportunities to get to that as well in the future.

We typically use Selenium and Appium in automation and testing by first identifying which modules we are able to automate. Then, whenever we encounter some new course in the framework that we're using, and we need to use a hybrid kind of framework, we will use Selenium to resolve it. 

We are still testing Selenium HQ.

The client is based in the U.S. They process the code checking, and we work on the script.

When we get storage or requirements for manual testing, we begin the automation once it is stabilized.

We work for a client who does HRM solutions. They wanted us to develop their scripts using Selenium HQ. Typically, we develop UI, API and database scripts. These are the three combinations we have used for them. So their test cases are typically where we initially do some operations on the various applications they have. Then, once the operation is done, we initiate a few API calls and then we validate the data in the database. This whole process of trying to enter into, listen into, and close is done using Selenium HQ. This is what we are doing. We have close to 8,000 test cases in the last three years.

The primary use of this solution is UI testing.

We use Selenium HQ for automation and API integration.

Selenium HQ is used by our organization to automate test scripts for our applications as well as to automate or regression tests carried out during software development.

In my company, I use the tool for testing web browsers.

We basically use the product for two things. The first is for testing for a website. The other thing is for repeating actions so that you can repeat the same action over and over with ease and without having to repeat the original steps. 

We are using Selenium HQ as a plugin within Visual studio and we develop in C#. We use the Visual Studio IDE and Selenium is our solution for automation testing.

I use Selenium HQ to streamline our regression testing procedures and minimize the amount of manual testing required, we chose to automate our entire regression suite. This includes all of the flow cases, as well as various other test cases, such as those for UI testing and negative and false validation tests. We automated a wide range of test cases to maximize efficiency.

We are using the solution as a trial at the moment and have not implemented it for customers.

We are using Selenium for web application automation and mobile automation.

We primarily use the solution in a web environment.

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.

Our company is a customer of Selenium and I work in QA.

We primarily use the solution for automation testing.

We use it for test automation. We are also using Cypress for some of our automated tests. We've tried Selenium a little bit, but it depends on the project we are doing.

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.

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

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

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