Try our new research platform with insights from 80,000+ expert users

Broadcom Agile Requirements Designer vs Tricentis qTest comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Sep 16, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Broadcom Agile Requirements...
Ranking in Test Management Tools
8th
Average Rating
8.0
Reviews Sentiment
6.2
Number of Reviews
21
Ranking in other categories
Application Requirements Management (7th), Test Design Automation (3rd)
Tricentis qTest
Ranking in Test Management Tools
3rd
Average Rating
8.4
Reviews Sentiment
7.5
Number of Reviews
18
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of October 2025, in the Test Management Tools category, the mindshare of Broadcom Agile Requirements Designer is 3.2%, up from 2.9% compared to the previous year. The mindshare of Tricentis qTest is 14.4%, up from 13.3% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Test Management Tools Market Share Distribution
ProductMarket Share (%)
Tricentis qTest14.4%
Broadcom Agile Requirements Designer3.2%
Other82.4%
Test Management Tools
 

Featured Reviews

Hosney Osman - PeerSpot reviewer
Integration capabilities enhance testing and workflow automation
I rate Broadcom Agile Requirements Designer as 8 out of 10. It will be very nice if Broadcom has questions or comments related to my review and can reach me via email to clarify something. I want to be a reference for Broadcom. I don't have any information regarding the visual modeling function specifically. I'm not dealing with modeling requirements or generating optimized test cases in Broadcom Agile Requirements Designer. Broadcom takes a lot of information from us as end-users, and they provide fixes within two to five days maximum. My team has raised many enhancement requests and discussed them with Broadcom, and they are adding some of these features to the product itself. I look forward to receiving an email regarding these reviews, and I can add anything later if I forgot something, earning some points for this contribution on the website.
SamuLehikoinen - PeerSpot reviewer
Efficient and collaborative software testing providing comprehensive test management capabilities, seamless integration with various tools and impressive manual regression testing features
The user interface has a somewhat outdated design, which is certainly an area that could be improved. Some of the modules appear to be loosely connected, but despite these aspects, our overall experience with the tool was positive. When you begin integrating your testing tools with qTest, the available examples may not be very clear, and I believe this is an area that could be enhanced, particularly in terms of providing clearer integration guidance. While the tool's integration with various testing tools is impressive, there is room for improvement in showcasing more cases and benefits, especially through additional videos and documentation.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The modeling is a game-changer."
"It takes away all the time to construct test cases, so it is all automatic now, but it also levels the playing field."
"The most valuable features of Broadcom Agile Requirements Designer are ease of use, saving time for the team who builds test cases, and visibility of test cases."
"Technical support is excellent. They provide solutions quickly for issues encountered."
"The ability to create models/diagrams at multiple levels (nest/embed them) helps in taking models from high-level business requirements and building them into detailed requirements models and test models. Plus, it helps reuse lower level models. It also allows maintaining models at appropriate levels, even for very complex systems/solutions."
"Defects can be traced in the solution."
"CA ARD has some beautiful features which I haven't found anywhere else. For example, when designing or creating our test cases and doing scenarios, we are able to restrict our flows. If we take a data link between two processes, we can actually restrict it, so that, in production, if our functionality breaks down, we can restrict that and all the flows related to it will be removed from the test data set."
"It gives us an idea of creating the visual diagrams, which are quite easy to use. It is helpful in creating our business processes."
"The test automation tracking is valuable because our automated testing systems are distributed and they did not necessarily have a single point where they would come together and be reported. Having all of them report back to qTest, and having one central place where all of my test executions are tracked and reported on, is incredibly valuable because it saves time."
"The JIRA integration is really important to us because it allows our business analysts to see test results inside the JIRA ticket and that we have met the definition of "done," and have made sure we tested to the requirements of the story."
"I found the reporting aspect to be the most valuable as it provided a comprehensive overview of the efforts needed and the workload for individual tests."
"The initial setup was very easy."
"The most important feature which I like in qTest manager is the user-friendliness, especially the tabs. Since I'm the admin, I use the configuration field settings and allocate the use cases to the different QA people. It is not difficult, as a QA person, for me to understand what is happening behind the scenes."
"I like the way it structures a project... We're able to put the test cases into qTest or modify something that's already there, so it's a reusable-type of environment. It is very important that we can do that and change our test data as needed..."
"Being able to log into Defects, go right into JIRA, add that defect to the user story, right there at that point, means we connect all of that. That is functionality we haven't had in the past. As a communication hub, it works really well. It's pretty much a closed loop; it's all contained right there. There's no delay. You're getting from the defect to the system to JIRA to the developer."
"The main thing that really stuck out when we started using this tool, is the linkability of qTest to JIRA, and the traceability of tying JIRA requirement and defects directly with qTest. So when you're executing test cases, if you go to fail it, it automatically links and opens up a JIRA window. You're able to actually write up a ticket and it automatically ties it to the test case itself."
 

Cons

"A template in App Test should be created in advance. This has proven to be time consuming. The process is not fully automated, because there is a lot of manual intervention is required."
"At present, there is no option for test data parameters from ARD for virtual databases. We have to create them in TDM and push them as well. Virtual database connectivity needs to be improved. They need to come up with some areas where they can create synthetic data parameters easily from the test cases that have been designed."
"They do not have an engine to house test scripts to really pull together the testing pieces of it."
"Integration with Agile management tools can be improved, i.e., mainly test case maintenance and linking test cases to the automation script."
"The solution could improve security and authentication."
"I think it's already coming, but it needs more automation aspects. There is a tab for Automation, but I think it's not robust. I think that it's going to be a crucial element of the tool."
"Broadcom Agile Requirements Designer could improve the UI. Other solutions have a much better UI. The new UI should have a new modern framework."
"Data flexibility is something which I would like to see, along with more integration with App Test."
"You can add what I believe are called suites and modules. I opened a ticket on this as to what's the difference. And it seems there's very little difference. In some places, the documentation says there's no difference. You just use them to organize how you want. But they're not quite the same because there are some options you can do under one and not the other. That gets confusing. But since they are very close to the same, people use them differently and that creates a lack of consistency."
"I would really love to find a way to get the results, into qTest Manager, of Jenkins' executing my Selenium scripts, so that when I look at everything I can look at the whole rather than the parts. Right now, I can only see what happens manually. Automation-wise, we track it in bulk, as opposed to the discrete test cases that are performed. So that connection point would be really interesting for me."
"Reporting shouldn't be so difficult. I shouldn't have to write so many queries to get the data I'm looking for, for a set of metrics about how many releases we had. I still have to break those spreadsheets out of there to get the data I need."
"We feel the integration between JIRA and qTest could be done even better. It's not as user-friendly as qTest's other features. The JIRA integration with qTest needs to mature a lot... We need smarter execution with JIRA in the case of failures, so that the way we pull out the issues again for the next round is easy... Locating JIRA defects corresponding to a trait from the test results is something of a challenge."
"The Insights reporting engine has a good test-metrics tracking dashboard. The overall intent is good... But the execution is a little bit limited... the results are not consistent. The basic premise and functionality work fine... It is a little clunky with some of the advanced metrics. Some of the colorings are a little unique."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"For UFT to Tosca migration, scripts need to be rewritten as there are no automatic converters available."
"qTest offers a baseline feature where you can only base sort-order for a specific story or requirement on two fields. However, our company has so many criteria and has so many verticals that this baseline feature is not sufficient. We would want another field to be available in the sort order."
 

Pricing and Cost Advice

"At present, Broadcom works through partners rather than dealing directly with the consumer. When there are discounts given, it's up to the partner as to whether they want to give that discount to the customer. Sometimes, the partners decide to take the discount themselves. Pricewise, I would give ARD's price a rating of three out of five."
"The pricing model is based on how many people are using it. We have an annual license. There are not any additional costs."
"This tool reduces the cost associated with test cases, automation script generation, and maintenance costs."
"​The cost of the tool was well worth the benefit that we saw on the back-end."
"Recommendation is to go with concurrent licenses as oppose to seat license; this gives more flexibility."
"We were able to scale down some resources to basically self-fund our ability to purchase the tool."
"It is less costly when compared to other tools on the market."
"For me, pricing for Tricentis qTest is moderate, so that's a five out of ten. It's more affordable than my company's previous solution, which was Micro Focus ALM."
"We signed for a year and I believe we paid $24,000 for Flood, Manager, and the qTest Insights. We paid an extra for $4,000 for the migration support."
"It's quite a few times more costly than other tools on the market."
"Based on whatever I heard, I can say that Tricentis qTest is a little costlier than other test management tools, like Jira, Zephyr, or Xray."
"We're paying a little over $1,000 for a concurrent license."
"We're paying $19,000 a year right now for qTest, with 19 licenses. All the on-premise support is bundled into that."
"For the 35 concurrent licenses, we pay something like $35,000 a year."
"The price I was quoted is just under $60,000 for 30 licenses, annually, and that's with a 26.5 percent discount."
report
Use our free recommendation engine to learn which Test Management Tools solutions are best for your needs.
868,787 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Computer Software Company
22%
Financial Services Firm
13%
Retailer
11%
Manufacturing Company
6%
Financial Services Firm
14%
Manufacturing Company
12%
Computer Software Company
10%
Insurance Company
9%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Large Enterprise21
By reviewers
Company SizeCount
Small Business3
Midsize Enterprise3
Large Enterprise13
 

Questions from the Community

What is your experience regarding pricing and costs for Broadcom Agile Requirements Designer?
It's not affordable; it's very expensive. It would be suitable only for large customers, and a large customer will think twice before making a deal with Broadcom.
What needs improvement with Broadcom Agile Requirements Designer?
Integration with AI is an area that needs to be improved quickly. To be clear, this relates to how to use AI to improve use cases, break down applications, and review designs, as this area needs to...
What is your primary use case for Broadcom Agile Requirements Designer?
This solution saves a lot of time in the software testing cycle because, with Broadcom Agile Requirements Designer specifically, I am doing a flowchart, and I can extract test cases and use cases t...
What do you like most about Tricentis qTest?
I found the reporting aspect to be the most valuable as it provided a comprehensive overview of the efforts needed and the workload for individual tests.
What is your experience regarding pricing and costs for Tricentis qTest?
The solution is expensive. For the features that are available, depending on the volumes of licenses we get, we are able to get better discounts as strategic partners of Tosca. We can pass some ben...
What needs improvement with Tricentis qTest?
Customers are moving towards Tricentis due to their association with SAP. There is interest in understanding if there are connectors for converting UFT scripts to Tosca, as many customers are looki...
 

Also Known As

Grid Tools Agile Designer, CA ARD, CA Agile Requirements Designer
qTest
 

Overview

 

Sample Customers

Williams, Rabobank
McKesson, Accenture, Nationwide Insurance, Allianz, Telstra, Moët Hennessy-Louis Vuitton (LVMH PCIS), and Vodafone
Find out what your peers are saying about Broadcom Agile Requirements Designer vs. Tricentis qTest and other solutions. Updated: September 2025.
868,787 professionals have used our research since 2012.