I think it has stabilized a lot, but it's not the best tool in the market. It has a lot of room for improvement, but it has a very big community.

The stability is good. There aren't bugs or glitches. It doesn't crash or freeze. The performance is good. It's reliable. 

The solution is stable.

Selenium HQ is a stable solution. However, it depends on how the applications are identified. If the applications or objects are identified correctly then it is stable. Otherwise, we can have some glitches in the identification and verification.

It's a pretty stable product. There are no bugs or glitches. It doesn't crash or freeze. 

Selenium HQ is a stable solution.

It's a stable product.

Selenium HQ is highly stable.

Selenium is a mature and stable software. There are no bugs or glitches. It doesn't crash or freeze.

The product is stable. However, it is impacted by the changes in UI. I rate the stability a seven out of ten.

I rate the solution's stability a ten.

The solution is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. 

Of course, you need a lot of time to optimize your scripts so that they run stable.

So performance-wise, Selenium is the best tool so far. It has the fastest automating tools.

This solution is the most stable product I have used when it comes to web automation.

I rate Selenium HQ a nine out of ten for stability.

Selenium HQ is very stable. 

Selenium HQ is stable.

This solution has been stable. We have not experienced any issues with bugs or glitches.

We had a few stability issues initially but it's very stable now.

It's extremely stable.

The latest version should always be treated with care. Being open-source it can be unstable.

We've never had any stability issues. It's reliable. The performance is good. It doesn't crash or freeze.

I didn't have problems with stability.

The only as I mentioned is supporting the latest versions of the browsers. The code that works in FF doesn’t work in Chrome. Scalability wise, Selenium only supports the websites with pure HTMLs.

The tool is stable but needs to update to the new version of Chrome. 

The stability and performance are good.

The solution is very stable. I always suggest Selenium, even when conducting internal training. As I consider this to be a better solution than that offered by the competition and one which works, I do the same with my team. I always advocate on behalf of the ease of integration of Selenium HQ.

I find it a reliable solution for the most part. But in some cases it is only as reliable as the third-party code it works alongside with. For example, Selenium doesn't have automated generation code, so we are dependent on other tools for this. And as I have mentioned, we also need to use third-party tools for things like email-based applications.

There have been no issues with the stability.

Stability depends on how you write the code. If you handle all conditions, there will be some surprises. Suddenly, you will have pop-ups and other conditions. 

In the beginning, we had issues with several test cases failing during regression. Over a period of time, we built our own framework around Selenium which helped us overcome of these issues. 

Considering that a lot of corporations are using it, it has obviously gained quite a lot of trust from a lot of Fortune 500 companies that use it. It's considered very stable.

There have been no issues with the stability.

The stability is excellent.

So far, I have not have any issues with its stability.

No issues with stability. The Selenium community maintains it well.

Selenium HQ is stable.

We are satisfied with its stability.

The stability is evident and it is a good tool.

Selenium HQ is a stable solution.

I haven't found many issues related to stability - so far, Selenium HQ has worked wonders for me.

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

The level of stability depends on the version you are referencing. For example, Version 3.1.46 is very stable, however, Version 4.0.0, the latest version, is not.

I find Selenium HQ to be a stable product.

This is a stable and reliable solution for web applications, there is no doubt since it's an open-source tool, it's recommended for any web application. We used GitHub and Jenkins for continuous integration and everything is available online, we have experience working with the Jenkins version controls and configuration tools.

The stability of the solution has been good, it is reliable we have not had any bugs till now.

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.

There are some issues with the stability of Selenium HQ.

It is stable, but one issue I see is that whenever there's a new version coming in, every three months or so, the current version changes and the new version of Selenium is not stable and then we have to wait for a week or so to get a patch for that.

We use Selenium HQ on a regular basis.

Overall there are around 20 people working on this just in my area, who are also responsible for delivery as well as maintenance.

There were issues.

There were some stability issues with Selenium. Sometimes my tests were not stable.

I did encounter some stability issues. So, I found it was better to run automation scripts at slower speeds to get consistent results.

Due to its high rate in releases sometimes working code cannot be executed after an upgrade due to a new feature or different behaviour.

There were no issues with the stability.

No issues encountered.

I've seen latency issues in IE while executing scripts. The same script runs faster in Chrome and FireFox. Sometimes, the same xpath may not identify an object in Internet Explorer, but will identify it in Chrome/FireFox. So we have to write a different code in that case. This is not a very common scenario though.

Selenium has been giving us failures sometimes. It is not working one hundred percent of the time when we are creating elements. They need to improve the stability of the solution.

The solution takes a lot of time for the developers. For example, if we are trying to implement UiPath or Automation Anywhere the people who are non-technical can use these two solutions. Selenium HQ is not easy for someone that is new to use, it takes too long for developers to learn the solution. There are other solutions that do not require such a learning curve.

Selenium HQ is a stable product.

The stability of the solution is good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable.

We have not faced any issues in terms of stability.

There have been no issues with the stability.

No, usually it works perfectly fine in any platforms and languages. Fits any servers including Azure and has no problems to run the tests.

Selenium HQ is salable.

Stability has been a problem during my testing. I have run the same code several times and faced issues for no apparent reason. Problems were identified, though the objects are all in place and no changes have happened in the UI, the test failed unwantedly. Then, we run the test case for the second time, the result will be true. This means that there is instability in the tests.

Normally, the solution is stable.

To some extent it is unstable while executing against different versions of IE browser, but that could be overcome through some work-around and framework design. Edge browser executions are not stable as IE browsers.

I encountered some smaller stability issues, but most of the time it can be solved quickly. There are also some minor issues with parallel test executions but there are workarounds for this specific cases so it can be avoided.

It's a pretty stable solution but we have to be careful and make sure we're using what has been released. We need to know which version to use and make sure it's the latest one so we know it will be stable. 

As the various browsers change, tests stop working. But that can hardly be blamed on Selenium. Every problem I've ever had has always been answered by “Get the most recent version of Selenium.”

Stability has been fine for us.

No issues encountered.

We've had no issues with stability.

We've had no issues with stability.

I observed like batch execution issues and comparability issues like AngularJS app's etc.

It is stable.

Selenium's stability is good.

This is an open source, so some issues are always pop[ing up , but compared to other open source automation tools web driver is much much better.

There are stability issues, especially when Mozilla Firefox updates.

Sometimes there are issues with automation testing in Internet Explorer.

Currently WebDriver is having issues running against the latest of Firefox.

It has good stability.

Some times with timeout issues.

Yes, with Internet Explorer only.

Selenium is pretty stable, if not 100%.

The stability is a concern. Internet Explorer tests take three times longer to run and are a lot less stable than those run on Chrome, for example.

There were no issues with the stability.

It's been stable so far.

The stability of the solution is good.

I have not had any issues with the stability.