Requirements that are no longer in plan since last reconciliation -
I'm receiving a list of test cases under "Requirements that are no longer in plan since last reconciliation" after a reconciliation. However, when I view the referenced requirements vs. the actual collections requirements, all referenced requirements are still part of the collection. Why are we getting test cases categorized this way when reconciling?
|
One answer
A 406 status error is very rare. Please open a PMR for further investigation
|
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
BTW, this is for RRC 4.0.3
Hi Stuart,
Which RQM version I you using? Also can you elaborate a little bit about the whole scenario? After adding the Req collection in TestPlan was there any changes done to any of the associated TestCases or requirements?
We're running RQM 4.0.3. Some of the use case modules and associated requirements were originally imported from legacy word docs into given folder "locale"s. After this some of the use case names may have changed. But test cases had been written based on the latest names. Some of the use case names did not change. So i don't think this is the problem. If requirement in question link is followed, it is attached to a use case module which is called out in a collection. Non of our requirements artifacts are directly called out in collections but rather called out in use case artifacts (modules) that are called out in the referenced collections.
We also have a "Failed Reconciliation" on one requirement as follows: