Reviews (1-1 of 1)
April 11, 2018
Score 7 out of 10
It is being used by the quality control and quality assurance department. We have the complete CLM solution so Quality Manager is linked with Rational DOORS and Rational Team Concert to provide complete traceability. IBM Rational Quality Manager is also integrated with automation testing tools as well as security tools as well. The QA department manages their test plans as well test cases and script in the tool. Test Plans are linked with Requirement Collection in DOORS as well as sprint plans in RTC. Test cases are linked with individual stories and use cases. This integration and collaboration are helping us a lot.
- It's part of Rational CLM suite so provides seamless integration with the Change Management module (RTC) and Requirement Management module (Rational DOORS).
- It can be integrated with IBM Rational automation, performance and security testing tools which provides an easy way to schedule or execute the scripts from RQM console. Results are linked with test plans
- Provides Lab management facility, which helps to maintain, allocate and monitor your testing assets like test servers, devices etc.
- It provides good way to manage multiple test execution cycles. all execution cycles are linked with test plans.
- It does not provide any functionality for defect logging. For defects, you will have to have Rational Team Concert. So it's useful if you have the complete suite.
- Similar to defects it also does not provide builtin functionality for requirements. Requirement module needs to be purchased separately .
- It does not have query builder like in RTC, where a user could define its criteria and see the results easily. There is some mechanism to filter the results while you browse test plans and test cases but it's not very user-friendly and sufficient.
Read Qaiser Islam, SPC4's full review
It gives more results if you are using it as a part of complete CLM, as a suite standalone it lacks many features. The missing requirement and change management part make it very hard to use with other CLM components. Also if your development environment is complex and you need to link different versions of test cases with different stories or a different version of requirement artifact, global configuration functionality helps a lot in this case.