I would rate this solution 8 out of 10. 

Learning is easy. Implementation is not as easy, but it is still better than other tools in the market right now. I'm giving it an eight because there are a lot of things Selenium is not supporting. The rest of technology is changing, but they are not changing along with it. Normally, if we are writing a complex test, we have to do a lot of workarounds, which isn't good when we are writing scripts.

I think it's very easy to screw up with Selenium if you're using it for the first time. If you are getting it for a large organization or large project, it makes sense to have some professional help.

I'm just a consumer or end-user. 

We deploy on the cloud and on Jira as well.

I'm working on the latest version of the solution. 

I'd rate the solution an eight out of ten. If they fixed the reporting functionality, I'd rate it higher. 

I would recommend that anyone who is looking to implement Selenium into their organization should have strong technical knowledge. At least one person should have some programming language skill set in either Java, Python or C#. 

Selenium libraries are a tool that could be reused, but how to frame, integrate and optimize by reducing a line of code to get the proper maximum efficient output requires technical knowledge. It is valuable to have experience prior to joining the Selenium HQ community.

Overall, I would rate Selenium HQ an eight out of 10.

Each product has its own pros and cons. It is very customizable, but then you have to have a lot of knowledge about Java or an object-oriented programming language that works with it. They keep creating frameworks to make your life easier, and it is a very customizable framework, but you have to have the knowledge to be able to do it. There are other tools out there, such as Worksoft, for which you don't have to know Java.

If you're starting from scratch, it would be good to get a good Java developer and make him or her get everybody up and going. That Java developer can train junior test automation people. You should hold on to that person for as long as you can. Getting a good Java person is probably critical when you're creating your Selenium framework.

It is not the easiest thing because it is hard to get a quality assurance resource that is knowledgeable about Java. So, it is very difficult to get a good framework in place. Usually what happens is that you'll get QA people who start doing QA, and then they start doing test automation. Once their skills get up there in Java where they're decent, they move over to being a software developer. So, they get out of the QA world, and they go over to be a developer. So, you lose that talent. You had to do your framework, and now they're gone. Maintaining good talent is difficult. It is hard enough to maintain the Selenium framework, and when you start losing people, it makes it harder. The next person comes in line, and it is just a revolving door. 

I would rate Selenium HQ an eight out of 10 because it is not perfect, but it is the best tool out there to do automated testing.

This solution is good to use if the application that is getting identified for the objects is able to uniquely identify the properties. If this process works well then it is good to use. If it is a web application, they can use this solution, but if a desktop-based application is involved, then they should look for another solution.

I rate Selenium HQ an eight out of ten.

The framework and the language should be defined early if a new user plans to take this solution on long-term. It helps to have that figured out so you can implement it correctly. A few years back, I started with Java, however, given the choice, I would have preferred Python.

I'd rate the solution ten out of ten. 

If it is not a large project or application, Selenium HQ is a good choice; however, if the application is large and you want to maximize coverage, I believe you should look into tools like Katalon or Ranorex, or something that allows you to do more scripting with less coding.

I would rate Selenium HQ a seven out of ten.

I rate Selenium six out of 10. If you want to use Selenium, you need basic programming skills in Java, .NET, or Python as well as knowledge of the TestNG framework. You should know how to identify the object from the application and use the developer tool. 

It's one of the best tools I have worked on. It's a strong tool and a winner in functional testing and automation testing. It's open source, and it also supports mobile testing. Other tools, such as UFT, are quite expensive. 

I would rate it a 9 out of 10.

My advice to others is the first step to using Selenium HQ is to learn a programing language.

I rate Selenium HQ a nine out of ten.

It's a very stable tool and it's open-source, and there are new versions available. The new versions come quickly and frequently, you receive a successor version with bug fixes very easily. The tool is easy to use and highly configurable.

We are customers. 

I'd advise users to take advantage of community posts. If the person finds any trouble, Google it. Probably someone already has found the same issue and also has found the solution or the workaround for it.

In general, I have no complaints about this product. I would rate it nine out of ten.

It's crucial for technicians to thoroughly evaluate whether the solution aligns with the end-to-end application needs, especially considering the complexity of enterprise applications. For leveraging features like ERP integration or mobile testing, it is better to understand the compatibility and support for specific devices.

I rate Selenium HQ a seven out of ten.

I recommend the solution to others. Its learning curve is very high for Java and comparatively less for Python. Apart from this, it is highly stable. A lot of documentation is available for it in case of any queries. I rate the solution a nine.

I'm an end-user. 

The solution is okay, however, you need to use it together with the TestNG and with Maven and use different plugins that improve it.

I'd rate the solution nine out of ten.

I rate SeleniumHQ seven out of 10. When you're choosing a solution, it depends upon the type of applications you are using in your project. If you have only have desktop and mobile, go for Selenium. However, if you have multiple applications like Windows-based applications, a virtual machine-based application, or a mainframe .NET application, I suggest going with another tool, like Tosca UFT.

I give this solution nine out of ten.

When it comes to UI testing this solution is perfect but for API automation it lags behind compared to Postman.

Around 70 percent of our engineers use this solution on a daily basis.

Since the solution is open source you can create a user account on GitHub and receive free community-based technical support when it is required.

Selenium HQ is deployed on-cloud in our organization.

Overall, I rate Selenium HQ a nine out of ten.

You need to be aware of Selenium HQ's architecture. I rate it a ten out of ten. 

I would recommend this solution to others if they have short projects or short-term goals, where you do not have to automate. If we have only one month for testing, we should not automate it first. If we want to automate web applications, Selenium HQ is the best tool because it supports multiple languages, browsers, and operating systems, and it's open-source.

There are multiple features the solution has that I haven't worked on.

I rate Selenium HQ a six out of ten.

I am at the beginner's level, working alone to get some more practice. It will take some time to have more experience with this solution.

Micro Focus is more user-friendly, and they offer paid support.

I would rate this solution a nine out of ten.

It's important to get hands-on experience with the program. I would also suggest getting your frame pyramid in order. You need to decide on the language you're going to use and have that programming language support in your organization and decide which other tools you're going to use. Also, think of your application and whether Selenium is the appropriate solution.  

This is the most widely used tool throughout the world in this space. It has so much support available and is a benchmark for other tools so I rate the solution eight out of 10.

I would rate this solution 8 out of 10.

My advice for those who want to start using this solution is to analyze the project very well and choose the right tool for the project. For small projects, choose Selenium. It's the best option.

It must be evaluated very well before being used. In my case, we implemented a front-end that facilitates the use. If you want to use it in the future I can give you some access.

My advice to anyone considering using Selenium is that using their libraries is good but the focus should be on finding the elements. Element location is a tough part. There are plugins that are available so don't waste time creating your own locators. You can use ready-made built-in solutions that would reduce your time a lot.

On a scale of one to ten, I would give Selenium HQ a six.

I'd rate the solution six out of ten. It's not an out-of-the-box solution like Oracle or SAP. 

I would advise potential users to contact their IT guys because they will have a problem setting up the first automation. Of course, if there are people like me who want to develop their own knowledge, I would say they need time to get to know how to use it, optimize the process, etc. 

But if not, it will be easier for end-users to start with some kind of RPA offering by different vendors because they have their tools prepared for the end-users, for onboarding, and so on.
Because these open-source tools are still tools made for developers and IT guys, not for end-user.

On a scale from one to ten, I would give Selenium HQ a six.

I would rate the product an eight out of ten. The product is easy to use. 

This is a Java-based product so the version is tied to your version of Java.

Overall, this is a good product and I recommend it. It is easy to use and works well once it is set up, although support requires research and you need to have some coding skills to use it.

I would rate this solution a seven out of ten.

We implement the solution for our clients, not simply resell it.

The solution is very easy to implement. The first step which must be done is to go through the documentation on the site. I feel the solution to be pretty straightforward and people are drawn to it by its ease of use. There is always help available on the web for integration or implementation issues.

I rate Selenium HQ as an eight out of ten.

I would surely recommend others to use Selenium as we do, especially because while using Selenium we can use Java concepts as well. It's great that, through Java, anybody can use Selenium; even novice programmers. In today's market, automation is a big part of every organization, and Java programming skills can hugely enhance the use of tools like Selenium.

One of the biggest lessons I learned was during my time as part of the development team. I didn't want to work in the manual testing team and so when my development project was completed, I moved to the automation department because I wanted to carry on being productive. With this move, I realized that I could easily learn other tools and technologies that are useful in the market, by adapting my programming skills in Java, Python, or any other programming language, to working with tools such as Selenium. In addition to my Selenium work, I also now do Rapid Automation as an automation engineer.

I would rate Selenium HQ an eight out of ten.

I would say start lean, gain small wins and incrementally add more. Example: Start automating test cases for one browser and slow expand to multiple browsers.

I would recommend this solution to anyone considering implementing it into their organization. Overall, I would rate SeleniumHQ an eight out of ten.

Just go for it. 

We use the on-premises deployment model.

I'd recommend Selenium, but it depends on the client's use case. As it is a free solution, users are able to cut a lot of costs. They can bring in developers that are experienced with Selenium, and those developers can build it up, scale it up and then, later on, you just need a few people to maintain it. It's a great option that allows companies to refrain from paying all sorts of license subscriptions that are quite exorbitant.

I'd rate the solution eight out of ten.

You just need to choose the solution which best suites for you.

I would rate Selenium HQ an eight out of ten. Selenium HQ is good for a web testing application.

I don’t see it as a company spending money on anything. I like to keep up with the market because I built my career around test automation.

Most important criteria when selecting a vendor: 

• Ease of implementation
• Ease of adaptability
• How much skill set would be required to operate it. Can I take somebody with no programming background and get them up and running on it, or does it require a heavy-duty programming background?

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

In order to use Selenium HQ comfortably, you need to be very strong on Java skills. I would give Selenium HQ a rating of seven out of ten.

On a scale from one to ten, I would give Selenium HQ a seven.

If you are wanting to do some web-based automation, definitely Selenium HQ is a good solution. I would rate Selenium HQ a six out of ten.

I would rate Selenium HQ an eight out of ten.

I would recommend anyone thinking of implementing Selenium HQ to go for it - it fits into every format, depending on your time and skillset. I would rate Selenium HQ nine out of ten.

We are a customer and an end-user. We don't have a business relationship with Selenium.

We have the solution deployed both on-premises and on the cloud. 

I'd rate the product at a nine out of ten. We've been very happy with the product. 

The reason we are using version 3.14.1 and not the latest version is that this version is the latest most stable option. The most recent versions are often not the most stable. 

I'd rate the solution at a six out of ten.

There are lots of tools in the market that are paid versions, such as QTP. Those have got lots of features. While Selenium has some good features, due to the fact that it's free, you cannot get support, which is why I have reduced my rating by a few points. 

It is a straightforward application to learn. If you know Java, it is something that can be easily learned and used. It has a lot of support out there. But again, it might not support some of the older back-end platforms. I would rate Selenium HQ an eight out of ten.

In Selenium, you have to write extensive code - even if you want to automate one login scenario, you have to write a code of around 50 lines - which uses a disproportionate amount of man-hours. It takes such a long time to use this solution that it may be worth looking into other free solutions such as TestProject or Katalon Studio, or paid solutions to replace it.

Before implementing Selenium, I think it's very important to find out the maximum resusability of the code using the parameterized XPaths.

I would rate this solution as seven out of ten.

I would recommend this solution. If working on multiple browsers and on multiple platforms is the goal, then Selenium is definitely the right tool because it works on Windows as well as on Linux. It also supports multiple browsers. 

I rate the solution eight out of 10. 

I would recommend this solution to others.

My advice to others is that, first of all, you have to understand the process of automation from a general point of view, and how people get on with the coding and all that. If you only have manual experience, like a lot of new testers, then you likely don't have much experience in coding either. And in that case, my advice would be to first understand the logic of the process. For instance, before jumping into it from the deep end, try get a handle on a few small steps first, and as you go along you will learn the basic coding, the basic architecture, how Selenium works, how the automation process works, and so on.

Then, take a piece of code and ensure that it works as a standalone script, then finally jump into the framework. Develop from any framework, use it as best as possible, get some experience with it, and try to become an expert from there.

You can use any programming language you prefer. As for myself, I'm using Java, but you can use C#, Python, Ruby, PHP, etc. There's a lot of support for different programming languages with Selenium. 

My biggest lessons while using Selenium have had to do with automation and how it really works, which is something I've always been interested in. Once I get an application, any application whether it be a WAVE app or mobile app, I very much enjoy getting stuck into the automation part of testing. And what I've learned is that not everything is that easy to automate.

In many cases, I have had to team up with new solutions and play around with code on my own, which has been a great learning experience for me. Apart from that, with Selenium I have been able to implement new things such as OCR (Optical Character Recognition) which is useful when you are not able to find all the elements you need, and I feel good that I was personally able to enhance the automation process with what I have learned along the way.

I would rate Selenium HQ an eight out of ten. 

I have worked full-fledged on Selenium WebDriver along with the multi-tenancy for the JavaScript framework.

I have hands-on experience with the Selenium framework, and I also worked on, API for APA automation Currently I am working in the healthcare domain.

In my opinion, it is a complete end-to-end solution.

As of now, it's for only web APIs. It provides a complete solution. 

I don't see that it's many disadvantages, except when doing the coding. A person should have perfect coding skill sets. If they don't have a coding skillset, it's a little difficult for them to get started. 

We had completed multiple POCs to present to our clients.

It was pretty straightforward for me. I didn't experience a lot of difficulties getting into Selenium. If your framework with Selenium is good, then it gives you the correct output.

I would rate Selenium an eight out of ten.

My personal advice is that it is such an amazing tool to work on. The best thing about the tool is the community support. I don't think any other tool has that kind of a community support. You just post a question on any popular community, like Stack Overflow, and you get answers in like 20 minutes. There are so many people using it which makes life really easy. At the same time, you get a lot of free hands to work on. Meaning because it's based on Java which has so many open source libraries, you can use any library to do any kind of functionality you want. That's a pretty powerful tool. My advice if you get stuck somewhere, is to just put it on community and then you get your answer.

On a scale of one to ten I would rate Selenium HQ an eight.

I would advise you that it's a good tool to automate UI. There have been issues in the product.

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

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.

Implementing an automation tool for Quality assurance has become the latest trend in many organisations.

1. The biggest challenge is to identify whether there is really a need for an automation tool. Incorporating automation requires a robust product which undergoes minimal changes during its lifetime otherwise the automation scripts would require constant change.
2. Selenium only supports web based applications and it is not suitable for testing small sized products which can be easily tested manually. The effort in incorporating an automation framework would be larger than testing it manually.
3. User should have good knowledge of any of the programming languages supported like Java, C#, Ruby / Python to build an automation framework.
4. Building an automation framework can be used easily across team with minimal training.

If you have developers that can operate Selenium HQ then this solution will be a good fit. However, if your developers are new to Selenium it might be better to choose another solution.

I rate Selenium HQ an eight out of ten.

I would recommend using Selenium with Python, it will be helpful.

I would rate Selenium HQ a seven out of ten.

We are just a customer and end-user.

I'm not sure which version number we're using. However, it is a version from 2020, from the last year or so.

I'd advise those considering the solution, if you want use SeleniumHQ, it's a good option if you have good developers that understand the tool and can make changes in the tool. If you have the right people on hand, it works very, very well.

I'd rate the solution at a seven out of ten. If it didn't need such technical expertise, I might rate it higher.

In summary, this is a good product. If it is a web application that you are testing then this is the best option.

I would rate this solution a seven out of ten.

The product has record and play back tool but it is always better to write your own code and implement the framework.

Just try it.

I rate Selenium HQ a seven out of ten.

My advice for anybody who is considering Selenium HQ is that if there is a timeframe that is separate from the automation then it is suitable. However, if there is no timeframe and the issue does not fit into the automation, and it needs to be adapted manually, then this product is not a good choice.

I would rate this solution a six out of ten.

I would advise others to only use Selenium in a unit test environment, and not an end test environment. It's very technical; you need a programmer and/or a developer to create your scripts. If you do not have development skills, then you will not be able to create scripts, at least in Selenium.

I'd rate the solution seven out of ten.

It's an open source product, (probably) the most popular one in a whole software test automation industry. Although it's free and open source it has good support and great integration with different technologies.

If you have a good QA team with engineers which have strong technical background and experience in software development I would definitely recommend you Selenium WebDriver. It offers everything you need, you can make your own framework and architecture, based on your business and technical needs.

If you have non-technical QA team and you want test automation - Selenium WebDriver is not the right solution, you should invest in some commercial products which are easier to use and don't demand that level of technical skills from your team.

The solution requires good understanding of Python, Pearl or Java and it's important to use the documentation. It would take a few hours of watching video sessions or reading the documentation to get started. It also helps to have an understanding of how API works, the architecture and how Selenium interacts with browsers. Having the background helps to design something with more features. 

I would rate this solution an eight out of 10.  

We're using the on-premises deployment model.

It is an open-source solution and you are able to build vertically. There is also lots of support pertaining to Selenium such as videos on YouTube. It's very easy to integrate on different platforms.

The solution is constantly being updated and advanced; it's very reactive and in a constant state of change. 

I'd rate it seven out of ten.

Learn how to use the “Page Model” approach to creating tests. If you code direct to the Selenium API and don’t using the Page Model, as things change in your web application, it will become more and more difficult to update your test to reflect the changes.

If you are using it for the automation test, automation is generally good. If you have an experienced developer, it will be really good to deploy the open-source frameworks for Selenium.

I would rate it a seven out of ten. 

Not a ten because they don't come loaded with the frameworks or different framework options. You have to build it from scratch. The build-in comes with a lot of networks and libraries and stuff. You still need to build that framework before you start writing the code

They try to come up with new features. I think they're in a very good space.

You'll have a lot to do when automating many different applications. Just practice.

Make sure you get the set-up right initially.

I would rate this solution a seven out of ten.

You'll be good to go with this.

I would recommend this solution to others. I would rate it a seven out of 10.

I would rate Selenium HQ nine out of 10. If someone is thinking about adopting Selenium HQ, I would encourage them to use it. However, you do need to be reasonably proficient in Java, C#, or C++.

Just use web driver and enjoy.

An engineer from any background can learn and build automation easily.

To use Selenium WebDriver effectively user should have good knowledge of programming language, this is one of the main complexity. Using Selenium you have to write test framework using your favourite language and some additional tools should be used also (like Jenkins for CI and reports), this is the first step which should be done.

Go for it. This is one of the best open source solutions I know of.

You need a person who knows one programming language thoroughly. It is not like anybody can pick and work on this solution. You should be thorough enough on the language and the framework that you are choosing. Only then Selenium HQ is the way to go.

I would rate Selenium HQ a seven out of ten. 

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!

There's nothing much to complain about Selenium, barring a few shortcomings. The Selenium IDE plugin – http://www.seleniumhq.org/projects/ide/, records your clicks and you can export this recorded test case to code in Java, C# etc. Though the converted code is not entirely stable, it certainly makes life easy when it comes to writing test cases.

The library is nicely done. The webdriver communication with the browser is not perfect, though, especially IE. The longer the test is the higher the chance it will break down. It's impossible to reach 100% stability with more complicated tests. Very likely that the problem lies within Internet Explorer, not within the webdriver.

Very good for testers with programming experience and web developers, not so much for regular testers, unless they are given a “ready” framework and shown how to write tests.

If you don’t have a budget, go with Selenium because it has a huge community and the versions are constantly updated. Also, it supports latest browers most of the time, and major competitors are using it. It’s reliable and extendable. When it comes to performance testing, you can use the same code for both Selenium and JMeter.

Please remember it is just a tool and not everything can be automized.

We use the on-premises deployment model.

It's a mature product that has been on the market for ten years.

I'd rate the solution seven out of ten.

A few features such as synchronization techniques, cross-browser coding, and customized reporting need to be implemented.