What constitutes a "suspect"

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:

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:

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: