I have not seen any issues on that side of it. In three years, I have seen only one unplanned outage. Other than that, everything has been great. I have not seen any performance issues.

We are just setting up the environment. We have had some issues with load generators disconnecting. There is probably going to be room for improvement there. I understand that nothing is perfect, but if we are seeing that already, we rather not just see it.

I haven't seen any issues with stability during six to eight hours of continuous exhibition. There were no packet drops due to connectivity issues or any problems with regard to line monitoring.

The product is more stable compared to other vendors like NeoLoad and JMeter.

I haven’t seen any stability issues. The stability is good.

We don't have any issues with stability. 

This is a stable product and as far as we're concerned, there is no other choice on the market.

I like the product. It's very stable. There are no bugs or glitches. It doesn't crash or freeze. It is reliable.

It is very stable.

Over the last couple of years, it's been evolving. We started using more in the last one year and we see it's pretty stable. Adding new features to StormRunner is going to slow down once it has every feature. That has to do with stability and I don't see any drawback in that.

The tool is not perfectly stable.

It is a stable solution.

The solution is stable.

It has been stable every time I have used it. We don’t put much stress on it since we have our own performance center and load generators.

I think it's fairly stable. There's some features that I think could be made better but, for what they have, I think what they have works well.

HP SaaS web application is pretty stable and no issues were seen during the evaluation process.

There was a bug and we opened a ticket with HP, and it was fixed after a few days.

I think the product is still immature because we have some problem reaching the mobile center connection related to a proper configuration on our machine. In fact, we are in touch with the R&D team to fix the configuration for our environment. I also think that it will be useful to have an object recognition tool because the specific configuration on the browsers are to be managed so as to fix our specific test. I need to recognize what was the configuration on the remit browser and I need a tool to analyze the impact of the browser configuration on the test.

I have worked extensively on the various module supported by STRL2.1v and provided my suggestions/improvements/recommendation to the HP R&D Team

Quite good.

During the initial days of high concurrency testing (300,000 and 600,000) we had issues with the StormRunner infrastructure e.g. graphs “disappeared” in the middle of a test, and HP had to give an online fix. Also, there were cases where tests appeared as “initializing” even though it actually started and HP again had to give an online fix. The StormRunner R&D team was very proactive in fixing the issues in very small turnaround time and supporting us running the high concurrency tests.

It's stable. It's not perfect, but it's stable.

No issues with stability.

We have had no stability issues.

No issues encountered.

No, the only thing I remember seeing as a “bug” when you hover your mouse over the graph, it will jumps around and doesn’t follow the mouse movement, other than that I don’t remember seeing anything from a stability perspective.

This is a new product, so there are a couple of flaws, sometimes things act up weirdly. We reach out to the support group, they solve the issues. It's an ongoing process. We understand that.

I have found this to be a very stable product.

Yes, it's stable. We don't have any issue right now with the performance or anything like that.

No issues with stability.

It's been stable.

No issues with stability.