The support is very good. They have excellent community support.
The pricing is pretty good.
The stability is okay.
The support is very good. They have excellent community support.
The pricing is pretty good.
The stability is okay.
There are still some glitches that they need to improve. We have given support feedback as well when we have some issues. They're very responsive and they do work to fix and improve issues.
LoadRunner offers a full protocol, whereas, with this product, only a few of the protocols are supported - not all.
I've used the solution for five years.
We do occasionally deal with glitches. The previous versions are very stable. The newer versions have some glitches and sometimes it hangs, however, for the most part, it's okay.
There are issues around some protocol settings, like when we use encryption. When a person uses the banking application, the user and password are encrypted. We have issues with the encryption protocol. Lately, some settings may have changed and it seems to be working.
While it's a good solution, I cannot speak to the scalability.
The community support is good. Whenever we have an issue, they provide support to resolve it. If we need information about features, they help. Support is very good.
We use the solution as projects demand. We are a consulting company. Whatever the client has already purchased, we will use that. We work with all kinds of tools.
I don't have any details related to ROI.
I'm not exactly sure what the pricing is as it differs from client to client.
That said, LoadRunner is expensive and NeoLoad is less expensive whereas JMeter is free.
I'm familiar, for example, with LoadRunner. When you compare this with Load Runner, Load Runner is the best tool as it, number one, is very user-friendly when compared with the NeoLoad. It also supports the protocols. It is very mature, so people are very comfortable with it. The monitoring is good, and it has a lot of good features.
NeoLoad will not support all the protocols and it's not as user-friendly as LoadRunner. I use LoadRunner more than NeoLoad, and therefore am more comfortable with it.
I also am familiar with JMeter, which is an open-source option and therefore a free tool. In comparison, NeoLoad is a big tool and JMeter is quite small. With NeoLoad, you can get all kinds of reports, flexible reports and you can customize the reports as well. We can drill down on the reports if we want. That's not possible in JMeter.
NeoLoad is a good tool for banking or telecom applications. When compared with the LoadRunner, NeoLoad will support almost all necessary features including reporting. It is a good tool.
Overall, I would rate the solution at a six out of ten.
Used for performance testing of applications on QA environments as well as production environments. NeoLoad is best tool for testing in production without making many changes to the script or solution.
It helped in achieving the testing of on-premise applications, as well as cloud-based applications, without much difficulty.
NeoLoad does not support Citrix-based applications. Neotys should take a look into this protocol.
No issues.
No issues. As far as Neotys NeoLoad, it is excellent in scalability.
The support is good.
We started with NeoLoad.
The initial setup is easy.
The implementation was done in-house.
Our ROI is 100%.
The licensing cost is less compared to other licensing performance testing tools.
We tried JMeter, but due to its support (which we found subpar), we had to switch to NeoLoad.
You will love NeoLoad moving from open source and code-based performance tools.
All-in-one product (design, runtime, results), easy scripting and variable correlation, and load generators deployed all around the world to simulate global traffic.
It is easier to do load tests using NeoLoad.
The only improvement that I wanted is support for load tests in agile mode. Neoload 5.2 makes this possible by updating the old versions of scripts with data from the new HTTP requests.
I have 4 years of experience.
The only issue that I had was with network virtualization on load generators installed on Windows Server 2008 R2. The link is sometimes cut between the controller and the load generators.
10/10. Support is available, they handle issues very quickly, and they are very skillful.
I used HPE LoadRunner. I think that NeoLoad is more user-friendly.
NeoLoad is easy to deploy using the install wizard.
Well, first I got trained by a vendor team. After that, I implemented more projects using NeoLoad.
My advice is that there should be a minimum of 4GB of memory on the servers on which you are installing NeoLoad.
Neotys provides a free evaluation licence to use NeoLoad with up to 50 virtual users and all protocols included.
The product licence remains cheaper than HP LoadRunner, for example.
It is convenient to be able to keep up the pace in which the application code was delivered to us. Since we manage nearly 500-600 applications and we need to make sure they are tested, we wanted something robust with an option to check against previous baselines with minimal human intervention without sacrificing criteria.
We wanted something with less risk when incorporating or shifting scripts.
The fact that it loads from an external cloud is a plus as well.
It took just a few minutes to set up Neotys Cloud, as opposed to a few days with other solutions.
They are coming out soon with NeoSense. It's a hybrid between app management tools and a testing tool. This will be helpful for us because we'll be able to monitor applications within various different environments. This is precisely what we have wanted.
We've been using it for a year.
We had no issues with deployment.
We used to have only 50 online users. Later we moved to where we are.
We have used their gold support option. Yes, we have been happy. They usually answer between 36 and 48 hours for non-critical issues, and with critical issues they hold your hand.
We did it in-house.
We didn't negotiate the price. To give perspective, we went from spending three million dollars to 160 thousand dollars, which is a huge saving and good value.
One of our goals was to find a platform that would have the functionalities that we were used to while incorporating in other ones. ProLoad was a competitor, and one other (can't make out name).
We wanted it to support agile and devops, while being able to upgrade to a number of releases over the course of a day, so it was a fit.
The company really strives on experience, always making sure that I as a customer am happy. For example, my team at Dell had an issue with our new version, which we had just updated to. Another team used a different version which required different protocols, and there were discrepancies between the versions. The company found out that our errors were user errors, and helped us fix the problem.
I helped them in terms of product development since we at Dell told them requirements and they added that to product life cycles. So we are a customer, but told them some requirements we'd like to see.
We use Tricentis NeoLoad for performance testing purposes, like load testing and stress testing.
Tricentis NeoLoad is quite easy to use as compared to JMeter. The other valuable features of Tricentis NeoLoad include correlation, parameterization, load testing, and file parsing.
Tricentis NeoLoad crashes if an application contains more than 1,000 scripts. Tricentis needs to improve in this area, and the solution should run smoothly even if thousands of scripts are imported into it.
I have been using Tricentis NeoLoad for one and a half years.
I rate Tricentis NeoLoad a nine out of ten for stability.
Around 10 to 12 users are using Tricentis NeoLoad in our organization.
I rate Tricentis NeoLoad an eight out of ten for scalability.
The solution’s initial setup was easy.
Tricentis NeoLoad can be installed in ten minutes.
Tricentis NeoLoad is not an expensive solution, but it can be quite expensive if we need a license for load testing, depending on the organization level.
On a scale from one to ten, where one is expensive, and ten is cheap, I rate Tricentis NeoLoad's pricing a seven out of ten.
I would recommend Tricentis NeoLoad to other users.
Overall, I rate Tricentis NeoLoad a nine out of ten.
This solution is mostly used by our customers to monitor the performance of the networks or of the server site.
We appreciate that this solution is very user-friendly, even if the user does not have a lot of protocol knowledge and experience.
We would like to see the addition of one-to-one integrations with the Tricentis Tosca suite to this product, which would then cover the end-to-end needs of our customers who are looking for a single vendor solution.
We have been working with this solution for 11 years.
We have found that the only stability issues, when using this solution, stem from the hardware in operation as opposed to the solution itself.
This is a fairly scalable solution.
We have found this solution to be very time saving for our customers, who report optimal resource usage since its implementation.
The licensing for this solution is renewable yearly, and covers all available features and technical support.
We would rate this solution a six out of ten.
We use Tricentis NeoLoad for performance testing across our product lines.
My company has a good experience with Tricentis NeoLoad, and what I like best about it is that it lets you generate loads from different geographies. The load generation agents getting placed on different geographies is a very good feature of the solution.
I also like that you can scale up Tricentis NeoLoad very quickly.
The general feedback on performance testing with Tricentis NeoLoad for all product lines within my company is good.
An area for improvement in Tricentis NeoLoad is its price, as it has a hefty price tag.
We've been using Tricentis NeoLoad for about three years.
Tricentis NeoLoad is a stable solution, and my company didn't have any problems with its stability.
Tricentis NeoLoad is a scalable solution. It tests performance, so it has to be scalable.
Technical support for Tricentis NeoLoad is good. My company hasn't had many issues with support. If I were to rate support from one to five, my rating would be four out of five.
Tricentis NeoLoad is a solution that's easy to set up. Deploying it wouldn't take much time, as deployment could be completed within just a few days.
Pricing for Tricentis NeoLoad could be cheaper because, at the moment, it's expensive. For a year, the solution cost us a lot of money, in particular, more than $50,000.
I'm using the latest version of Tricentis NeoLoad.
In my company, two people from the performance testing department use Tricentis NeoLoad.
My rating for Tricentis NeoLoad is eight out of ten.
My advice to others looking to start using Tricentis NeoLoad is that it's a good product, and it would be money well spent.
My company is into product development, and it's a user or a customer of Tricentis NeoLoad.
There are several key features, including Jenkins integration, infrastructure monitoring, and results analysis.
Implementing this product has allowed us to increase the number of projects that get load testing, and the frequency by which we re-test our performance.
It needs improvements in the UI. It's currently not as friendly as it should be.
We've used it for seven years.
We haven't had any issues with deployment.
We have never experienced any isuses with stability.
The product has scaled very well up until this point.
The support from Neotys is very good. Responses are timely and come from experienced, knowledgeable load testing professionals.
We previously, and still use JMeter for some projects, in addition to Neoload.
The initial setup is straightforward for basic usage. The setup for higher volume load testing is more involved, but I wouldn't say complex, as should be expected for an enterprise class load testing tool.
We implemented it with our in-house team.
It's priced based on the numbers of VUs, virtual users, that your needs require. The free edition gives you 50 VUs. The pricing is fair for high-volume licensing. Cloud VUs can be rented on-demand for bursts of higher capacity testing needs without permanent purchase.
We looked at JMeter and Webload.
I highly recommend understanding load testing concepts before using any automation tool.
I basically agree with this review. The 'Other Advice' is one of the most valuable parts. Whatever you are using, you need to understand what you are doing. A representative load test environment and sufficient coverage of the application being tested are often ignored, producing test results that will not predict the performance of your production environment.