It's actually complex. It's not really straightforward, but it depends on what you're actually building for your organization. We have built a wrapper around it for other teams that are actually consuming it.

Initially, you build a solution around it, which is a challenge. If you are trying to build a standalone automation with Selenium, it will be a challenge.

There isn't a set deployment. If a team wants to use it, they can start using it from day one.

It's an internal website that we work on.

The setup is pretty simple.

We do not really require some technical person for the maintenance of Selenium HQ. That said, sometimes, due to certain issues, like dependency on certain versions, you have to change the entry in your pom file. Otherwise, certain open-source things don't work well with the latest version of Selenium. The backward compatibility for certain other open-source software and APIs don't work well with the latest version of Selenium. You have to have little backward compatibility also. Other than that, I found it was pretty stable with almost all the other open-source software. It didn't require constant watching.

The initial setup of Selenium is easy, usually taking two to three hours to complete.

When I first came here, the framework was in place, but it was more basic. There is a team of three guys here, and we're all pretty smart. We're the excellence team for the framework. We've done a lot to make it a lot simpler for us to create our test cases. Three people probably worked 25% of the time for a few years on it. So, a lot of time was invested into the framework, and it has come a long way. It is much more sophisticated now.

Maintaining the architecture and Selenium framework for testing requires work. It is an ongoing kind of process. We're constantly maintaining it and updating it.

Selenium HQ's initial setup was straightforward. However, the integration part took some time.

I rate the initial setup of Selenium HQ a four out of five.

The solution offers a very easy initial setup. It's not overly complicated or difficult. Compared to Appium, for example, it's much easier. 

I'd rate the ease of implementation five out of five. 

The initial setup is very simple.

Maintenance is required. 

The scripts we must maintain require a significant amount of upkeep.

The initial setup is effortless. We only need to download Selenium HQ from the Oracle site and follow some steps, then it's installed. You install the correct version for Java and configure Selenium. It's complex compared to Tosca, but if you have some knowledge on the programming side, you can easily do it.

The time needed for deployment depends on the code, the complexity of the application, and the number of restrictions you have. Deployment takes around 30 minutes to an hour.

Its initial setup is a little tough. It could take around six hours, but if you are experienced enough, you can do it within an hour. If you are a complete beginner, it will be a little difficult.

You have to be really good with the POM dependencies, and you have to be used to working on different IDEs, such as IntelliJ or Eclipse ID. Based on the different setups, you have to consider the POM file and also integrate those dependencies. These things take up some time initially, but once they are done, it works well. I would rate it a 4 out of 5 in terms of the setup.

It doesn't require much maintenance. If you are upgrading to a new version, the basic changes will be needed, but not that much maintenance is needed. It's really easy. They do a release every six or seven months.

The initial setup of Selenium HQ is very difficult. You need different configurations on your system, such as Java and you need to configure it. Additionally, you need to have some IDEs such as Eclipse or IntelliJ IDEA on your system. Selenium is supported in many languages, such as .NET, Java, Python, JavaScript, and C#. So, at least you must be knowing any one of these languages, then only you can use Selenium.

The solution requires coding experience to be able to implement.

The deployment does not take a lot of time. You can create a continuous integration pipeline with TeamCity or Jenkins, and then you can run tests.

The initial setup was not quite so complex and also not simple. I tried it in Eclipse, and it didn't work quite well, and then I tried it in IntelliJ. I need to look further into it if either can be used with Selenium. I didn't use it with Eclipse. I used it with IntelliJ. With IntelliJ, the implementation was pretty straightforward, pretty simple. However, with Eclipse, it's not.

The initial setup for mobile app testing, especially when installing simulators, is complicated. Configuring simulators for Android and iOS platforms is time-consuming due to trial and error. Setting it up for mobile automation takes approximately one to two weeks. However, for web automation, the process is comparatively straightforward. It takes less than an hour to complete.

I rate the process a seven out of ten.

The solution's initial setup takes time. I rate the process as one. We require a specialist to download and install it manually. Later, we need to create a framework and set it for an automation process. The entire process is quite complicated for new users.

It was not very easy to set up. 

We needed to add a lot of plugins like TestNG and Maven. The whole configuration was not very easy. I am not sure if it is the Selenium setup or just the whole system setup.

Setting up SeleniumHQ isn't that complex. We like to develop our application in Pega and have a point cloud that we deploy on Google Cloud. It is developed and tested with Jenkins, which is a continuous integration tool. Once the code is specific to Jenkins, we trigger Selenium and execute the scenarios. After this finishes, we move everything to cloud. 

Along with this docker, there is a deployment phase in Google Cloud, where the images of our application are moved to pre-production. Pre-production is something like a replica of production that allows the users to work on it. So once it is transferred to pre-production, the users will work for one week or one or two. If they are satisfied, we move on to production.

Deployment usually requires about eight to ten people. Most of the work is done by technicians who are akin to database administrators. They take this on for one month a year every year. Their job is mostly to minimize the weight of the application. In the next phase, DevOps engineers deploy the enviornment. The time for deployment depends on the teams and the tasks. If there is a small change, it may have taken between half an hour and an hour. On the other hand, if there is a significant upgrade of the application, it may take eight to ten hours. Generally, we don't need any maintenance unless a UR application has changed.

The initial setup is easy, like a walk in the park for any user.

The level of ease to set up Selenium HQ is medium. You need to have experience in order to do the initial setup.

Selenium HQ was not difficult to set up. We can use management tools allowing us the ability to directly add dependency without having to install Selenium HQ.

The initial setup was fine. It didn't seem to be complex.

The difficulty was with the web interface and finding the objects. I have to inspect elements and this times time.

I am still in training but will improve in the next few months.

The initial setup is easy but it requires certain development skills to set up. Without that, it's not easy. The difficulty is in creating a framework and that requires thinking about the maintainability and scalability aspects.

Unfortunately, I find it difficult. I am a nontechnical person and each time I set up Selenium, I need to read a little bit of documentation. There are too many integrations with different tools.

The initial setup can be very complex.

The initial setup was straight forward. We don't use it in deployment, we just use Selenium for testing in our organization. The code which was deployed was tested before.

There are four developers in my team who are working on it.

It was not a Selenium deployment because the deployment was of code, and we only use Selenium for testing purposes. We did not deploy with Selenium code anywhere on production.

The solution isn't difficult to set up. It's quite straightforward. 

I'd rate the ease of setup eight out of ten. 

I cannot recall exactly how long the deployment itself took. 

Sometimes there may be some maintenance required around upgrades. You would need to check the compatibility between the software, for example. That said, the maintenance requirements are pretty low. It's not complex to maintain the product. 

The initial setup is complex. I think some changes were done, but it's still too complicated for end-users. 

Building the framework is the one thing and using selenium (which is straightforward) after that is much easier.

The solution's setup is easy in the local environment but complex on the server side. You need to also update the Chrome version in the cloud before setting it up in the local environment. 

The initial setup is fairly easy. It requires you to install their IDE, which is Eclipse. In total, it takes between three and four hours to deploy.

The initial setup of the deployment cycle and the process of onboarding users takes an average of 10-15 minutes. This is the length of time it takes for us to set up in our pipeline the data repositories for the regression suite, and, subsequently, integrate the data with Selenium HQ, which is the point at which we run it.

The initial deployment was simple, as we are not doing anything too complex with it. We're using Azure DevOps for the deployment, so we test for that with a test plan and build up the pipeline accordingly, so we can execute and get the test execution report in order to find out what other test cases were impacted, and what other test cases we need to resolve. Doing it this way, we can easily find and fix any bugs in the deployment.

It was difficult to some extent, but with good documentation from the on-line community we where able to implement the tool.

We use Python, so the initial setup of SeleniumHQ was quick and simple. You can use any browser or tools like, Chrome, Firefox, or Edge to run the automation testing. 

The initial set up requires a bit of research because it's not straightforward. You need to be a developer to be aware of how to set it up. As an open-source tool, you do need to have some kind of background knowledge on how to implement it. Basic deployment takes about a week or two.

It was easy to set-up.

The initial setup was straightforward and easy. The deployment time takes around two to three hours.

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.

The initial setup was straightforward, and deployment took five months.

The initial setup is very simple and not complex.

The initial setup of Selenium HQ is straightforward.

The initial setup is pretty straightforward, so long as you have the correct plugin. I would rate the setup experience 4.5 out of 5.

The initial setup is not complex or hard to do. It's pretty simple and straightforward. A company shouldn't have any problem implementing it. 

The initial setup is pretty straightforward and simple.

You first have to install Java, JDK, in your system. Then you can install an editor such as Eclipse. In Eclipse, you can incorporate all the Selenium jar files.

Selenium HQ is not complex to work with.

Selenium is comparatively difficult to set up and requires technical knowledge in order to integrate and configure it. I developed a complete, fully-functional framework for this solution, which took around eight months to automate around 100 test cases.

We've been using Selenium for a long time and haven't had many issues; we knew how to configure it. It's not completely straightforward and implementation takes time but everything was available on the internet and the blogs. There's a lot of documentation available regarding deployment. 

The initial setup is little complicated the installation could be simplified.

The setup of Selenium is easy, in my experience, since it is provided as JAR files that you can download. Apart from that, there is, I believe, an architectural approach where you can simply input your dependencies and it will automatically download all the JAR files needed, and other required files.

As for deploying the code, this is just as easy. For example, if you're working with some type of continuous integration, it's a breeze to deploy. First, you have to build up your framework, and then you can deploy it to Git, or GitHub, or anywhere you want. At this point it's just about uploading the code, so there's not much to it. 

Clear instructions were provided to complete the installation. It was very straightforward. There were no issues when installing this solution.

APM setups are a bit more of a challenge. It takes longer to set up APM.

There were no issues in the installation of WebDriver. From the end-to-end process to deployment, to the automation code.

The initial setup was pretty easy. There is lot of online documentation and online help. Even if you get stuck somewhere it just takes a few searches to figure out the issue because there is good community support.

Selenium Grid set-up is bit complex.

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

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

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.

The set up was fairly easy. I started creating scripts and running them on my local computer. In time, as soon as the script number went up, I started running them in the cloud.

It was straightforward. All we needed was an editor like Eclipse and all the required JAR files and driver executables. All these are available online.

The installation is straightforward.

The initial setup is straightforward.

It took half a day to deploy.

One person is enough to maintain this solution.

The initial setup is not straightforward. It's pretty complex.

It's complex due to the fact that you need to download a complement for the web browser and you need to recall the tests and you have to load the files. When you do a recall, the tools create a file with the steps. Before you need to playback, you need to load the file. It's not easy. You need to know some things about the tool. 

The deployment took maybe six months to possibly 10 months.

You only need one person for deployment and maintenance.

The initial setup is straightforward.

The set up is straightforward if you have a programming background.

It’s really easy to set up Selenium tests. Usually you need to make a framework which you can you as a part of setup project in any project later.

The initial setup of Selenium HQ is difficult in many areas, such as the framework.

I rate the initial setup of Selenium HQ a three out of ten.

The initial setup of Selenium HQ was easy. However, I was not directly involved.

The initial setup was complex and it took us approximately five days to complete.

If you've dealt with the solution before, it's fairly easy, but if you are new to Selenium, you will find it complex to implement. It's not a simple click-to-install product.

Deployment times vary depending on a company's rights and frameworks as well as the application deployment environment. If you have to do it from scratch, and you have to build a development pipeline, then it takes several days, and possibly even weeks. If you already have a development pipeline, and you just have to install the Selenium web line onto a machine, then it's done in five minutes.

Basically, to start with setup is straightforward and easier. If you use the remote web-driver, it is slightly complex to make the setup.

Initial setup is complex just as any other development project setup is. Selenium has no installation files, it's just a bunch of libs which you need to import in your favorite IDE and set it up. It really depends on your experience, but no, it's not that complex.

The very first setup several years ago was quite complex, nowadays it is simple. Generally we use Maven, so it is simply importing and doing the setup. If I already know the settings, it can be deployed within half an hour. It depends on the system configuration so there can be issues sometimes. Setup can easily be done internally and if there are good community people there could be a one-stop solution layer where installation is one click. Maintenance is only required when there are updates or API changes. 

The initial setup was straightforward, however, it does depend on what the organization's requirements are. Deployment can take up to one or two months.

The initial setup is pretty straightforward, but when you branch into using the Selenium Grid, things do get a bit more complex. It is all pretty easy now that I know how.

We set up the entire framework around how the tests would be and different class structures. Then we evaluated how to construct labs and how to title execution and stuff like that. It took us good four to five months of two or three people working on it, to set up a robust framework.

Straightforward by using Selenium IDE.

It was not too complex, however, it would be complex for someone who doesn't know much about automation.

The initial setup was straightforward. I was able to add the packages that I wanted and quickly get started with development in a day.

It's simple to set-up.

It is not complex. I don't remember the time it took, but I do have development and testing experience. So, for me, it was an easy ramp-up.

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.

 It very straight forward and easy. Of course it’s required basic programming skills.

To use Selenium WebDriver effectively you should have good knowledge of programming language, this is one of the main complexity

It was pretty straightforward. It needs some degree of programming knowledge.

It is complex, but they have detailed documentation, which is helpful.

There are a lot of test frameworks that support Selenium.

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

You need a basic understanding of the any particular language such as Java, C#, PHP to get started with Selenium. If yes, getting started with Selenium is pretty easy. Takes less than an half an hour to get started.

It took some time. I had to create, wrap and decorate a lot of its functionality.

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

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

The set-up was straightforward.