We are introducing agile development (SCRUM) in our department and being responsible for the quality of the product, it does worry me when it comes to the testing. Mind you, I was working in a SCRUM team for 3 years but in that company, nobody really cared and pretend it was “agile”.
As our product will require a lot of regression testing, a proper test case basis is a must. And here comes my problem – how to manage test cases if the stories might change / affect other stories? It would be tremendous amount of work to manually review all test cases that a story could affect.
An example:
Story 1: As a user, I want A
Story 29: As a user, I want B //that will, as a result, affect story A and its test cases might get invalid – e.g. adding more options, buttons..
Story 34: As a user, I want C // that might affect both A and B (e.g. change in calculations, UI layout, more options).
Except for proper description of the stories and hence clear mapping to other related stories, I cannot see any easy way how testers could make sure that all test cases are still valid. Is there any other solution or approach we should use?
Aucun commentaire:
Enregistrer un commentaire