Selenium HQ Reviews

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.

I have found using IDE and Cucumber framework is good.

I would like to see some reporting or test management tools.

I have been working with Selenium HQ for the past eight months.

The stability is evident and it is a good tool.

The scalability is good. On a scale of one to ten, I would rate it a nine.

When it comes to technical support you do have to go online for the support community.

Selenium only works with web-based applications, it does not work on desktops, or any Java-based, form-based applications. There is no automation for any of these kinds of applications. With the Oracle Application Testing Suite, it can do anything. Currently, it has some drawbacks in automating desktop-based applications. However, the main difference is Selenium only sticks to web-based applications. But Oracle Application Testing Suite, or any other testing suite, like UFT, can automate a form-based or desktop-based application.

The initial setup is very simple and not complex.

The pricing is open source.

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.

The primary use case for us is IntelliJ and IDEA.

The most valuable feature I have found is the bomb file and it is easy in its coding. It has a lot of capabilities and is compatible with many languages.

I would like to see a library of bomb files with an automated process and integration with Jenkins and Slack.

I have been using Selenium HQ for three years.

Selenium HQ is a stable solution.

Selenium HQ is definitely scalable.

Technical support consists of excellent documentation online.

Positive

The initial setup of Selenium HQ is straightforward.

Currently, Selenium HQ is free for customers.

I would rate Selenium HQ an eight out of ten.

I mainly use Selenium for web applications.

The most valuable features are ExpectedConditions, actions, assertions, verifications, flexible rates, and third-party integrations. I also like that it's an in-house solution, which means you're not dependent on any tool.

I find Selenium to be slow - its server takes a long time to interact with your browser and sometimes fails. It's also somewhat outdated, for example, it has no capacity to handle things like desktop pop-ups, does not support mobile testing, and has very limited reporting. In future releases, I would like Selenium to focus on headless execution when executing their test cases, using PhantomJS or Chrome Headless.

I have six years of experience with this solution.

There are issues with scalability in that it requires a technical person to perform it and takes a lot of time.

Selenium is open-source and has no technical support, but there is a big online community on platforms such as Stack Overflow who provide help for users.

I've previously used Node.js and Cypress.

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.

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.

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. 

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.

For me, the most valuable feature of Selenium lies in its ability to help us find elements quickly. Apart from that, the driver interface is really useful, too. When we implement the Selenium driver interface, we can easily navigate through all of the pages and sections of an app, including performing things like clicking, putting through SendKeys, scrolling down, tagging, and all the other actions we need to test for in an application.

One drawback to Selenium is that there is nothing like an object repository, such as that found in QTP, especially considering continuous integration practices that have become common nowadays. In future, if they can provide an object repository or some kind of repository for data, then that I would greatly appreciate it. For example, once you have the app credentials and all the other security data and you don't want to show them to other people who are not authorized, a repository for this kind of data would be very useful. You could then simply grant access to only those people who need it.

Another improvement I can think of is in the area of documentation and support. With Selenium, we're using freeware software, and because of this there is no support or anything from the vendor. In this case, you have to rely solely on your own coding experience and exposure to the tool, and you often have to search through many pages of code when you want to change something in your implementation. It also makes you rely on your problem-solving skills to a large degree, because some problems are not that easy to solve by yourself.

If I can compare Selenium with another solution such as SoapUI Pro, there's a big difference when it comes to coding your own solutions. With SoapUI Pro, if you want to fetch some data, you don't need to write any code or anything, and for someone with no coding experience, this makes it much easier to be able to use effectively. So, ultimately, more support for non-technical people would make for a great improvement in Selenium.

I have been using Selenium HQ for the last two to three years.

The stability of Selenium depends on the skill level of the team that is using it. If you are writing solid code for automating your scripts, then you will find that Selenium itself is a stable solution. But if you're writing sloppy code then you may find that Selenium slows down or becomes unstable. Truly, I think it all depends on the people who are using it, and how they approach the architecture of the framework.

I am hopeful that Selenium will scale well because, along with others nowadays, we plan to to move into cloud-based provisioning with continuous integration. We will be doing that with AWS, most likely.

I haven't taken any technical support till now because Selenium is freeware, and you will not be getting any technical support directly. So that could be something that they could work on because if they were able to provide support, it would great for us and many others. Without it, you can still add code to the Selenium software itself, but they won't be able to help you with it.

On the other hand, I do believe there is enough documentation online for anyone who wants to figure it out by themselves. There are videos, tutorials, and other resources available to us.

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. 

I am currently implementing Selenium along with a few other tools. For example, for mobile device automation, I'm using Selenium with Appium. The Selenium architecture can be integrated with Appium in order to be able to automate with mobile devices such as Android and iOS, which is what I'm doing now. Beyond that, we also have desktop applications; for Windows we have EXE files and for Mac we have DMG files. With these, I have implemented the Windows application drivers using Selenium so that we're able to easily automate any Windows-based or Mac-based app.

As for the rest of the team who are implementing Selenium this way, we have about 15 people on the testing side of things, and 6 people in automation.

Selenium is free software so we do not pay licensing costs. 

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. 

Selenium web driver - Java.

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.

Handling frames and windows needs to be improved.

I've been using it for one year.

No issues encountered.

No issues encountered.

No issues encountered.

9/10

Straightforward by using Selenium IDE.

We did an in-house implementation, doing our R&D over the internet.

Hot tool in market. Makes thing easier to use and implement. Demand increases cost.

Since it is an open source. It is free to use. However my company see it as the future of load testing.

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

Selenium is an open source automation tool founded in 2004 by Jason Huggins used widely for functional testing of web based applications. It supports multiple languages and browsers which gives it the versatility. Users can develop their automation framework in the language of their choice and test their product across various browsers. The most vital feature of Selenium Webdriver is, that it allows report generation with the help of TestNG.

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.

In the future releases I would like to see a support for testing images in web applications and a provision for identifying captcha.

There were no issues with deployment.

There were no issues with the stability.

There are no issues with its scalability.

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.

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

It is a good automation tool.

I would like to see Selenium HQ support legacy platforms.

I have been using Selenium HQ for the past five years.

I find Selenium HQ to be a stable product.

Selenium HQ is scalable for our needs.

Selenium HQ is not complex to work with.

We deployed in-house and it took between two to three weeks to complete.

The licensing pricing depends on the customer's needs.

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.

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

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

The solution is very easy to use. Once you learn how to do things, it becomes very intuitive and simple. It's quite a user-friendly product.

The interface is great.

We've had good experiences dealing with support.

The pricing is fine.

Handling configurations is very good.

The stability has been good.

It's an easy product to set up and deploy.

If a company wants to scale it, it can. 

The product offers a free community edition. 

Selenium has problems with some objects. The objects are not in the squares of the screen. The layout can be a bit strange. It makes it hard to find objects.

We'd like to see some more image management in future releases. 

We've been using the solution for two years at this point. 

The stability is great. We haven't dealt with bugs or glitches. It doesn't crash or freeze. the performance is good.

If you need to expand the solution, you can. We've never had an issue with scalability.

We have about seven people using the solution at this time. 

Technical support is great. They are helpful and responsive. We haven't had a problem with them.

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. 

We have found the pricing to be reasonable. It's not too high of a cost.

We are actually using the community edition, which is free. 

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.