Do we do BDD on Defects?
My team is moving away from Waterfall into Agile. As part of this transformation we are beginning to write requirements from User Story point of view. We are following the Discovery, Formulation and Automation model defined in eBook by 'Gaspar Nagy' and 'Seb Rose' and are implementing BDD. In Discovery phase, we are using Example Mapping
We have a bunch of Legacy defects (from Waterfall) which we are going to start adding to Sprints. Few questions on how to handle Defects in BDD
A) Legacy Defects
1. Should we do Discovery (Example Mapping) with legacy defects (similar to User Story Discovery/Collaboration)?
2. Should we do Formulation with legacy defects and add gherkin scenarios?
3. Should we convert legacy defects to user stories?
B) During Sprint
If bugs are found during sprint by Exploratory testing, should we write more Gherkin Scenarios to handle these bugs or is that an overkill?
C) Feature released to Production
If a user story is released to production and we find defects in production, how do we handle such defects
a) Do we do Discovery (Example Mapping) and collaborate on these defects
b) Should we write up new Gherkin Scenario for these defects?
d) If the bug is a corner case(rare case), do we still add/update Gherkin Scenario or is that an overkill?
Please sign in to leave a comment.