We performed a comparison between Broadcom Agile Requirements Designer and Tricentis qTest based on real PeerSpot user reviews.
Find out in this report how the two Test Management Tools solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."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 optimization technique helps in giving us the minimum number of test cases with maximum coverage."
"Integration with TDM, test data management tool, provides the ability to generate data or use identified (preset or parametrized) test data. It allows significant expansion of test coverage and flexibility, without creating new tests and needing to maintain them."
"In terms of meeting business challenges, it helped to shorten the dev/testing cycle by identifying requirements gaps early in the process, by having models shared within the development team. It helped increase test coverage and reduce the number of issues experienced by clients/customers."
"The modeling is a game-changer."
"The scale possibilities are endless, especially when combined with all the other products that CA has to offer."
"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."
"The most valuable feature is reusing test cases. We can put in a set of test cases for an application and, every time we deploy it, we are able to rerun those tests very easily. It saves us time and improves quality as well."
"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 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."
"UI and UX are pretty easy to understand without much of a problem."
"The solution's real-time integration with JIRA is seamless."
"qTest helps us compile issues and have one place to look for them. We're not chasing down emails and other sources. So in the grand scheme of things, it does help to resolve issues faster because everyone is working off of the same information in one location."
"What I found most valuable in Tricentis qTest is that it doesn't require installation. You use it through the URL. It also has an excellent reporting feature."
"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."
"It would help if it would save different subsets of test cases, use cases, etc., of a given diagram, for different purposes and provide an easy way to name those subsets."
"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."
"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."
"Integration with Agile management tools can be improved, i.e., mainly test case maintenance and linking test cases to the automation script."
"Data flexibility is something which I would like to see, along with more integration with App Test."
"The solution could be more user-friendly. For example, attachments could be icon-based to make it easier for the user to notice them."
"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."
"Needs improvement in aligning models so they look clear and readable without having to move boxes around."
"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."
"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."
"As an admin, I'm unable to delete users. I'm only able to make a user inactive. This is a scenario about which I've already made a suggestion to qTest. When people leave the company, I should be able to delete them from qTest. I shouldn't have to have so many users."
"Tricentis qTest's technical support team needs to improve its ability to respond to queries from users."
"I really can't stand the Defects module. It's not easy to use. ALM's... Defects Module is really robust. You can actually walk through each defect by just clicking an arrow... But with the qTest Defects module you can't do that. You have to run a query. You're pretty much just querying a database. It's not really a module, or at least a robust module. Everything is very manual."
"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."
"I wouldn't say a lot of good things about Insights, but that's primarily because, with so many test cases, it is incredibly slow for us. We generally don't use it because of that."
"The support for Tricentis qTest has room for improvement. The response could be better."
More Broadcom Agile Requirements Designer Pricing and Cost Advice →
Broadcom Agile Requirements Designer is ranked 10th in Test Management Tools with 20 reviews while Tricentis qTest is ranked 6th in Test Management Tools with 16 reviews. Broadcom Agile Requirements Designer is rated 8.0, while Tricentis qTest is rated 8.4. The top reviewer of Broadcom Agile Requirements Designer writes "Easy to use, beneficial test case visibility, and effective support". On the other hand, the top reviewer of Tricentis qTest writes "Puts all our test cases in one location where everyone can see them. qTest also allows the segregation of different types of Testing". Broadcom Agile Requirements Designer is most compared with Tricentis Tosca, Jira, TFS and Sealights, whereas Tricentis qTest is most compared with Tricentis Tosca, OpenText ALM / Quality Center, TestRail, Zephyr Enterprise and TFS. See our Broadcom Agile Requirements Designer vs. Tricentis qTest report.
See our list of best Test Management Tools vendors.
We monitor all Test Management Tools reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
