requirements coverage report failure in RQM 3 after refreshing DOORS 9.3 requirements
![]()
We are using RQM V3 connected to a Doors 9.3 database.
We have initialised a test plan with requirements by means of DOORS/RQM RQMi interface. Then we have refreshed that test plan several times to take into account changes in DOORS with no identified problem. This time, we have changed all of the requirements texts by inserting a string at the beginning of them. We have used RQMi again to refresh the RQM test plan. Requirements status in RQM were set to suspect which is the expected behaviour. We have cleared these statuses Then we have run the requirement coverage report and found it empty. We have checked test cases against links and found them ok in RQM. We selected one test case with 5 links, remove only one link and add it again. We have run the datawarehouse jobs and look for the requirement coverage report. All of the 5 requirements were found covered by the test case. Then we suspect something wrong with test case data after suspect status clearing. Any idea ? Do you know a mean to refresh all the test cases at once ? Thanks |
One answer
![]()
We have fixed our problem by running full data warehouse rebuild jobs thanks to Bernard Dupre:
Application Administration - Quality Manager / Data Collection Jobs / Data warehouse collection jobs Run data warehouse FULL collection jobs (see buttons under actions) (We had to refresh the web page several times before job details lines to be displayed) |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
I wrote here above: "then we have run the (plan) requirement coverage report and found it empty": this is to say: the report shows the correct number of requirements but no requirement is found covered by test case.
Later on, we found the same report with "no record found" message for a couple of days.
At the time of writing, we are back to the previous behaviour (requirements are found but without links). Without doing any thing.