It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Follow this question
Question details

×10,908

question asked: Apr 28 '10, 2:37 p.m.
question was seen: 4,306 times
last updated: Apr 28 '10, 2:37 p.m.

Related questions

FAQ - How this Forum works

What constitutes a "suspect"

0
Karen Steele (1.2k●2●135●139) | asked Apr 28 '10, 2:37 p.m.
Does anybody know specifically what constitutes integration with RQM and ReqPro to mark a test plan or case with the suspect value - we are not seeing the tool behave as we expected - we're wondering if only certain changes in ReqPro get mapped back as suspect as opposed to all changes to a requirement :roll:

3 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Mithila Nayak (86●7●2) | answered Apr 29 '10, 1:35 a.m.
Hi,
We have RQM-ReqPro integration and suspect feature works for us as expected. There are few steps that needs to be done to

1) Whenever there is any change for a requirement, you should either force synchronize or schedule synchronization to reflect the changes in RQM. You should see the modified requirement status become to 'updated' now.

2) You should have the test case/test plan linked to the requirements. Only then you can see the status of these associated test cases/test plan changed to "suspect".

Hope this helps.



Does anybody know specifically what constitutes integration with RQM and ReqPro to mark a test plan or case with the suspect value - we are not seeing the tool behave as we expected - we're wondering if only certain changes in ReqPro get mapped back as suspect as opposed to all changes to a requirement :roll:
0
permanent link
Karen Steele (1.2k●2●135●139) | answered Apr 29 '10, 10:49 a.m.
Hi,
We have RQM-ReqPro integration and suspect feature works for us as expected. There are few steps that needs to be done to

1) Whenever there is any change for a requirement, you should either force synchronize or schedule synchronization to reflect the changes in RQM. You should see the modified requirement status become to 'updated' now.

2) You should have the test case/test plan linked to the requirements. Only then you can see the status of these associated test cases/test plan changed to "suspect".

Hope this helps.


Thanks that's exactly what we do have, the question was however, what triggers the suspect .. what value in reqpro triggers that ? it is a change to text, description, attribute value changes ... anything or specific data ?



Does anybody know specifically what constitutes integration with RQM and ReqPro to mark a test plan or case with the suspect value - we are not seeing the tool behave as we expected - we're wondering if only certain changes in ReqPro get mapped back as suspect as opposed to all changes to a requirement :roll:
0
permanent link
Mithila Nayak (86●7●2) | answered Apr 30 '10, 6:37 a.m.
As far as I know its the text which triggers it. I am not sure about other fields.

Hi,
We have RQM-ReqPro integration and suspect feature works for us as expected. There are few steps that needs to be done to

1) Whenever there is any change for a requirement, you should either force synchronize or schedule synchronization to reflect the changes in RQM. You should see the modified requirement status become to 'updated' now.

2) You should have the test case/test plan linked to the requirements. Only then you can see the status of these associated test cases/test plan changed to "suspect".

Hope this helps.


Thanks that's exactly what we do have, the question was however, what triggers the suspect .. what value in reqpro triggers that ? it is a change to text, description, attribute value changes ... anything or specific data ?



Does anybody know specifically what constitutes integration with RQM and ReqPro to mark a test plan or case with the suspect value - we are not seeing the tool behave as we expected - we're wondering if only certain changes in ReqPro get mapped back as suspect as opposed to all changes to a requirement :roll:

Your answer

Register or to post 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.