Do we do BDD on Defects?
Hello,
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?
-
For me, defects or bugs are missed examples from a previous discovery session.
So from that, a discovery for the concrete defects should not be necessary, but if you thinks that there are more hidden issues, then make a new discovery session for it.
For Formulation, you should probably have all the necessary steps already. But perhaps not, then you need to do again some short formulation meeting.
But this all depends on details on how you work. But perhaps it is something to start thinking about how to do it for you.
0 -
Thanks Andreas Willich, how about exploratory testing defects? If a defect is found during exploratory testing in a sprint, should we write Gherkin Scenario (formulation) for such defects? Should we write Gherkin Scenario for every corner case?
0 -
Hi Andreas Willich, when you have a moment, can you please answer the question above? Thank you.
0 -
A defect found during exploratory testing is again for me an example that wasn't found during Discovery.
If you write a scenario for it and automate it, is a different question.
Personally, I am always thinking about the risk of an example. How risky is it if this fails for my project/product?
With automating everything you run in other problems (maintenance, flackyness).
When I remember correctly Gáspár Nagy is covering this also in our SpecFlow Masterclass. You can watch it in our SpecFlow School at https://specflow.org/school/bdd-masterclass/
0
Please sign in to leave a comment.
Comments
4 comments