Tricentis Flood Reviews

We procured the Tricentis Tosca enterprise version for test automation and with it, this solution was introduced to complete the performance testing and load testing. We are currently running performance testing with this solution.

We conducted Performance testing for the transformation project with the Flood tool

You can utilize this tool on the cloud, and also access application on-premises. That is a very good part of the solution.

The solution is not in an optimal state. During POC, we analyzed tool is kept on upgrading. The patch deployment is happening in parallel, things that are working today are not working tomorrow. We eventually sorted it out with help of CSM.

We integrated this tool with other software such as Azure client, but many times without a valid or visible reason, the connectivity was breaking.

Improvement suggestions-  The dashboard creation for the reporting needs to be easier. Currently, the solution does not support multiple script executions and we would like to see support for this.

We have been using the solution for approximately one year.

Tool service support is not very effective.  After following up with the account manager, we received a point of contact who could resolve the issues for my team, and that is working great. The associate appointed for this activity is helping us out to deliver our performance testing results. 

We started having less trouble when they appointed a dedicated person to us. He was able to resolve a lot of issues and is guiding us on how to use the solution.

Yes, have used Jmeter & Load runner previously. Suggest hiring Flood experts only to utilize this tool effectively.

It was a little complex to do the installation. We did receive some team training for upskilling and learning. However, this was very basic.

If you are new to the install you most likely would need experts. You will find that the integration and the setup are not straightforward. It is hard to ask your technical team to get information for the installation because it is limited, this is why it is best to hire experts. The full deployment took approximately three weeks.

If the solution had a cost it would not be a good investment.

The positive point we were able to achieve the objective as per plan.

Yes, we considered other tools as well. Was not able to consider other tools due to high cost and time constraints.

I will not say it is a bad product, I prefer to say it is an evolving product that has good potential in the future.

I rate Tricentis Flood a five out of ten.

We use the solution for performance systems.

The main value that we see in the product is the ability to have on-demand load generators in our cloud. We have our AWS or Azure cloud accounts which provides us with the feature to trigger load generators in our cloud. All the traffic is in our systems or in the cloud, there is no third-party connection from the tracking system resources. Having everything in our environment is the main benefit.

The solution lacks a little bit in the reporting features. Right now, the reporting test results that you want to read or you want to evaluate are pretty basic or too general. For example, If you want to check more deeply in an area that you found, hide responses, or maybe you want to tweak a little bit in how the results are shown, these are areas where the tool could improve. They are also missing the Microsoft diary application which would be useful if they could add in the future.

I have been using the product for two years.

We only had one issue a couple of months ago with the solution going down for a couple of hours. Other than going down once, we haven't had any kind of problems when it comes to stability, behaviour, or performance with the tool. 

The product has good integrations with other IT solutions. For example, Tricentis integrates well with AWS and Azure cloud accounts for modulation purposes. I think they're very good when it comes to scalability. As for the number of people using the solution, we have more than 70 testing teams using Flood right now which is hundreds of users.

Their technical support is awesome. It's one of the best things that they have. When we found a challenge or a problem, talking about the tool itself, the scripted part of the test cases or areas around those tools, we had really great support. They have the typical chat that you can find in a portal. For example, how Amazon might chat with you. They get an A-plus in this area.

We previously used IBM Rational and we switched over to Tricentis Flood mainly for the flexibility. Before with IBM, it was a legacy tool doing a performance in the old ways. It was pretty complicated and challenging at that moment. It was time for us to move to something more modern.

The setup was very straightforward. There were not any problems. We used an implementation strategy to deploy the solution, not because of the tools, but mainly because of the scripting part of the tool. In our test cases, we were using IBM's tool before and during the migration to Flood the scripts were completely different. When we moved to Flood we had to migrate hundreds and hundreds of test cases. We needed a plan for those scripts to be migrated, this required effort, resources and time. This was the hard part of moving to Flood when we deployed it. Setting up the configuration settings was not a problem at all and once we had the scripts it was pretty easy. You run it and that is it.

For the deployment and maintenance of the product, I am currently the only one working on it.

This solution is in the average price range compared to other testing tools. It's cheaper than LoadRunner and Micro-Focus which I know are pretty expensive, this is mainly because of all the features that you provide.

I rate Tricentis Flood a nine out of ten.

The most valuable feature is the support for Java, where we can quickly code what we need.

it is quite easy to maintain.

The integration with other tools is good.

The performance of the tool needs to improve. Part of the problem is that this is a cloud-based deployment in a firewall setting, and our application will also be online. This means that there is an inside firewall and an outside firewall, so it is a different IP between connecting and executing it. Sometimes we feel that it is this aspect of the environment that is delaying the responses, rather than the actual application.

The reporting needs to be improved. They should include some additional reporting components because compared to other tools, like Sovereign, it does less.

Integration with monitoring tools, such as SolarWinds, needs to be improved. We can get performance testing information into our monitoring tools, but we can't map information about monitoring to the performance testing.

We have had no trouble with crashes, although we have to keep monitoring the loads because every time we are planning to increase one, you have to notify them and then they will increase it. If we exceed the limit then it can get stuck.

Across multiple users, this is a scalable solution. However, across multiple platforms, we have to go in a different direction for that.

I think that technical support from the vendor is good. I would rate their service a four out of five.

I also have experience with Sovereign and JMeter. The reporting capabilities in these tools are better.

The initial setup is complex.

All of the features in this product are good.

My advice for anybody who is considering Tricentis Flood is that it is good for end-customer facing applications. However, it is purely result-oriented, as opposed to reporting-oriented.  It is good from a user's standpoint, but not fro ma senior management perspective.

I would rate this solution a seven out of ten.