Avoid Creating Stale Test Cases
SuspectivityA more focused approach is to use Suspectivity flagging in TestTrack to automatically flag changes across all linked artifacts. In your requirements flow, add an event to mark items as suspect or "possibly changed enough that they bear review".
Note the last check box in the previous screenshot. That allows updating of all linked artifacts when a requirement is marked as suspect.
To put it in action, all you have to do is right-click a requirement and apply the event. The mark will propagate down to linked test cases and runs automatically. When you open the requirement to begin writing your test or a tester starts a test run, you'll be notified of changes and can begin your investigation.
Three quick best practice ideas:
- Add the Is Suspect column to your TestTrack list windows, it'll quickly show you flagged issues.
- If you're a test manager, create a tabbed view that shows you currently flagged items.
- The traceability matrix can quickly show you flagged items and their relationships, and it's filterable.
Make it Automatic
Once you understand the functionality, you can leave it a manual process or add some automation to the mix. Use an automation rule to mark a requirement as suspect any time it's changed. I wouldn't recommend doing that for every requirement, so use a filter on the automation rule to only catch certain requirements. There are several possible filters you could use.
- Only requirements with existing links to test cases or test runs.
- Only certain types (e.g., functional requirements)
- Use a custom check box for minor changes and let the individual make that decision.