We performed a comparison between IBM Rational Quality Manager, TFS, and Tricentis qTest based on real PeerSpot user reviews.
Find out what your peers are saying about OpenText, Microsoft, IDERA and others in Test Management Tools."The one feature that has not allowed us to switch to any other solution is the integration with functional testing."
"It's very reliable as a solution."
"The most valuable feature is the RFT because it allows us to automate manual test cases."
"Latest features include versioning of testings which can be great when used for multiple releases of a product."
"It allows user to add whichever widget (predefined) based on the need. It has integration with CCM and RM to achieve traceability."
"Reusability and integration capabilities which make it a great choice for organizations that use a variety of development tools and platforms."
"RQM is something that we use everyday, so it has to be up and running, otherwise we would lose everything."
"RQM's best features are integration with test automation and performance testing."
"As far as queries are concerned, creating, grading, or customizing the queries as a primary requirement is very easy to do."
"The solution's iteration board is good because you can track all your work with it."
"TFS’s test management capability without the expensive licensing has large gaps. Users will be unable to access performance testing and coded UI testing capabilities."
"The tool's installation is straightforward."
"From the project management perspective, the tool is efficiently managing teams by giving management information, such as reports, graphs, velocity, capacity, etc."
"The most valuable feature of TFS is the central repository, and you can see what changes other developers did from which branch."
"The most valuable feature of TFS is the central repository, and you can see what changes other developers did from which branch."
"TFS' most valuable feature is the triage process. It is a robust solution that is easy to use."
"UI and UX are pretty easy to understand without much of a problem."
"Works well for test management and is a good testing repository."
"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."
"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."
"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."
"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 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."
"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."
"I think it's fine from a performance perspective but usability is something that needs improvement."
"RQM could be improved by adding a feature that allows test requirements to be selected when creating a task plan."
"Adding support for uploading a collection of test cases would be a helpful addition."
"While RQM allows for running tests and viewing results, it could be further enhanced in terms of performance and speed."
"Currently, the user interface needs to be more user-friendly."
"Organizing the test cases is tedious. There is no mechanism to keep and maintain the test cases as hierarchy. This should be seriously addressed."
"It would be helpful if we could assign a hierarchy to a group of test cases."
"Integration capabilities with other vendors' tools should improve."
"Overall, I think it would be useful to have something similar where Microsoft comes up with supporting concepts of scaling Agile in TFS so that clients don't have to look for a separate tool."
"The execution of test cases could stand improvement."
"Sometimes we feel that it need more CPU, and RAMs on TFS server, either we implemented the hardware with the product minimum requirements."
"The solution is stable but could improve."
"I would also like a true command prompt like Git."
"It would be better if we could bring it out on the cloud."
"Microsoft should discontinue the use of SharePoint as I don’t really see any value add to TFS, document management features can be included in TFS web portal itself, if required!"
"TFS's CI/CD, project pipelines, and management development could be improved."
"Could use additional integration so that there is a testing automation continuum."
"The support for Tricentis qTest has room for improvement. The response could be better."
"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."
"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."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."
"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."
"The installation of the software could be streamlined. We pay for the on-premise support and they help us a lot, but the installation is something which is very command-line oriented."
