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."Latest features include versioning of testings which can be great when used for multiple releases of a product."
"Reusability and integration capabilities which make it a great choice for organizations that use a variety of development tools and platforms."
"It's very reliable as a solution."
"Integration with the other professional tools is a very strong advantage, so that we can have a traceability between the requirements and defects in Rational Team Concert. That's the most important aspect."
"The one feature that has not allowed us to switch to any other solution is the integration with functional testing."
"RQM is something that we use everyday, so it has to be up and running, otherwise we would lose everything."
"It allows user to add whichever widget (predefined) based on the need. It has integration with CCM and RM to achieve traceability."
"RQM's best features are integration with test automation and performance testing."
"We use TFS for forecast management."
"TFS's best features include user-friendly test management, bug reporting, and ID assignment."
"Complete integration with VS IDE and Office tools: This give us a possibility of high-level automation, thus minimizing human error."
"I have found almost all of the features valuable because it integrates well with your Microsoft products. If a client is using the entire Microsoft platform, then TFS would be definitely preferable. It integrates with the digital studio development environment as well."
"It is easy to push our changes from quality to pre-prod and prod."
"The solution's iteration board is good because you can track all your work with it."
"The traceability is valuable. While managing the workflows, it was always nice to have that traceability from requirements and all the way through design. It integrates with Microsoft Test Manager, and you can have everything that is related to a requirement attached to it."
"The tool's installation is straightforward."
"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."
"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..."
"The solution's real-time integration with JIRA is seamless."
"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."
"UI and UX are pretty easy to understand without much of a problem."
"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."
"Works well for test management and is a good testing repository."
"Mainly Quality Assurance and DevOps, but of course the whole company and management areas with more knowledge of quality and client success approach."
"While RQM allows for running tests and viewing results, it could be further enhanced in terms of performance and speed."
"Organizing the test cases is tedious. There is no mechanism to keep and maintain the test cases as hierarchy. This should be seriously addressed."
"Adding support for uploading a collection of test cases would be a helpful addition."
"Currently, the user interface needs to be more user-friendly."
"I think it's fine from a performance perspective but usability is something that needs improvement."
"It would be helpful if we could assign a hierarchy to a group of test cases."
"Integration capabilities with other vendors' tools should improve."
"TFS's CI/CD, project pipelines, and management development could be improved."
"The user interface could be improved to make it simpler and increase usability."
"I only use 1% of the functionality, so I am not familiar enough to know what needs to be improved."
"The execution of test cases could stand improvement."
"Integration from Visual Studio could be improved."
"The dashboard needs more enhancements."
"TFS is scalable with different Microsoft tools for test management but it is not scalable with other third-party tools."
"TFS needs to be stable."
"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 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."
"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."
"The support for Tricentis qTest has room for improvement. The response could be better."
"Could use additional integration so that there is a testing automation continuum."
"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."
"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."
"The user interface has a somewhat outdated design, which is certainly an area that could be improved."