Question
How do you review and update tests with iterative releases and changing risks?
As software evolves so should our identified risks and tests, to keep them up-to-date, valuable, and relevant.
Do you regularly review your risks and use this information to update your existing tests?
How do you do this for your project? or organization?
