Marking items as suspect
If an item changes, related items may be affected. You can mark related items as suspect to indicate they need to be reviewed to determine if any changes are needed.
For example, if a requirement changes, test cases linked to the requirement may need updates. Marking the test cases as suspect when you edit the requirement flags the test cases to indicate the related requirement changed. Testers can click the flag to view the dependencies. See Investigating suspect dependencies.
The following items can be marked as suspect:
- Items linked using a link definition that allows dependent items to be marked as suspect.
- Requirements with parent/child relationships in requirement documents.
Note: The following information explains how to mark individual items as suspect. You can also mark all dependent items as suspect. See Marking all dependent items as suspect.
1. Click the Traceability tab when you are viewing or editing an item.
2. Expand a link definition to view the linked items.
3. Click Mark in the Suspect column for the item to mark.
The Mark as Suspect dialog box opens.
4. Enter the reason you are marking the item as suspect. For example, you may want to indicate the changes you made that impact the related item.
5. Click
The item is marked as suspect.
