Share your top 5 pain points using RQM
Please read on if you have used Rational Quality Manager (RQM) and want to provide feedback or want to share success story..
Please help us to serve you better by providing quality feedback on 5 top pain points (or things you like) specific to Rational Quality Manager or it's integration.
You can tell about e.g.
Thanks for your valuable responses which helps us to serve you better
Please help us to serve you better by providing quality feedback on 5 top pain points (or things you like) specific to Rational Quality Manager or it's integration.
You can tell about e.g.
- Feature Gap
- Day to day Usability issues
- Performance issues
- Reliability issues
- Complex feature to understand
- Anything else
-
I would like if RQM could...
Thanks for your valuable responses which helps us to serve you better
22 answers
Our Environment: RQM 4.0.3, DOORS 9.5.x, ClearQuest 8.0.x, RPE 1.2.1
Some Pain Points (I might be forgetting some important items, but this is what I have been dealing with recently):
- Integration between RQM and DOORS (through DWA):
- DWA is slow, so back-linking is slow when linking test cases to requirements.
- DWA has a defect that causes it to tie-up DOORS licenses indefinitely.
- The Reconcile feature shows "change" in requirements even if there are no textual changes in the requirement. (i.e. due to changes in test case mapping, etc.).
- The Reconcile feature is slow (again, because DWA is slow).
- RQM Formal Review of Test Cases and Test Scripts is cumbersome:
- It takes ~21 mouse clicks to approve one test case & test script pair (we use E-Sig since we are in a regulated industry).
- There is no way to configure approval of test cases to auto-approve associated test scripts.
- Prior approvals of artifacts allow an artifact to move from Approved to Draft to Under Review to Approved without needing to be reapproved in Formal Review.
- Reports take hours to generate from RPE (due to RQM API being a bit slow and due to DWA being really, really slow). Ex. A campaign with 443 TERs and 1575 requirements took several hours to generate a report in RPE.
- RQM interface requires a lot of mouse clicks to get anywhere/do anything.
- Performance when editing/executing large manual test scripts (over 100 steps) is poor.
Best regards,
Paul
page 3of 1 pagesof 2 pagesof 3 pages
Comments
Anandeep Sidana
Jun 20 '13, 4:21 a.m.Hi,
1.Test reporting is biggest challenge, creating custom reports on diff attributes there is no easy way. This is posing to be a show stopper to adopt RQM across group.
2.Test case execution when done individually in test suite, there is no way to filter already executed test cases nor any filters
3.Same test case can be added multiple times in one test suite.when add from selected test cases to be added,user never know that test case is being added more than once, Quality center creates another copy and there are better filters.
4.Getting folks adapt using RQM is very hard to convince especially when its transition from one tool ( QC) to RQM being not as very user friendly.
Harish Kumar
Jul 21 '15, 7:19 a.m.Is there a way to approve a test suite and by doing so, all the test cases and test scripts under that test suite get approved automatically?
Regards
Harish KN