What strategies do people use for keeping Test Cases up to date in Azure DevOps?

%3CLINGO-SUB%20id%3D%22lingo-sub-2703342%22%20slang%3D%22en-US%22%3EWhat%20strategies%20do%20people%20use%20for%20keeping%20Test%20Cases%20up%20to%20date%20in%20Azure%20DevOps%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2703342%22%20slang%3D%22en-US%22%3E%3CP%3EAt%20the%20moment%20test%20cases%20in%20my%20team%20are%20created%20per%20sprint.%20They're%20usually%20linked%20to%20a%20work%20item%20(but%20not%20always).%3C%2FP%3E%3CP%3EBecause%20the%20functionality%20develops%20and%20changes%20as%20the%20team%20iterates%2C%20tests%20often%20become%20redundant%20or%20out%20of%20date.%3C%2FP%3E%3CP%3EI%20can%20see%20there%20is%20a%20%22State%22%20field%2C%20which%20might%20be%20used%20as%20part%20of%20a%20process%20of%20keeping%20things%20up%20to%20date.%3C%2FP%3E%3CP%3EWhat%20process%20do%20you%20use%20to%20keep%20test%20cases%20up%20to%20date%20as%20functionality%20evolves%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

At the moment test cases in my team are created per sprint. They're usually linked to a work item (but not always).

Because the functionality develops and changes as the team iterates, tests often become redundant or out of date.

I can see there is a "State" field, which might be used as part of a process of keeping things up to date.

What process do you use to keep test cases up to date as functionality evolves?

0 Replies