--
You received this message because you are subscribed to the Google Groups "Behaviour Driven Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendeve...@googlegroups.com.
To post to this group, send email to behaviordriv...@googlegroups.com.
Visit this group at http://groups.google.com/group/behaviordrivendevelopment.
For more options, visit https://groups.google.com/d/optout.
Hi Stephen,I differentiate between scenarios and acceptance criteria. A criterion is a business rule. That might be something like:- Customers who qualify for refunds should receive the same amount of money they paid.
But a scenario is an exemplar; an example that illustrates the particular rule. So it would be something like:- Given Fred bought a microwave for £100 on 10% discount, when he asks for a refund then he should receive £90.Because you can think of the specific examples, it's now easier to see that there might be other scenarios too.- Given Fred bought a microwave for £100 with £20 3-year insurance- Given Fred bought a fridge-freezer for £200 (but it's still at his house)So you might end up with multiple scenarios per business rule, depending on how you phrase the different contexts.
More on that here. One of the most common anti-patterns I see is people thinking they've got scenarios when they've actually just got acceptance criteria phrased in Given-When-Then form. More usually I see acceptance criteria come into the 3 Amigos meeting (normally via the BA), then be turned into scenarios as the result of that meeting.
I also prefer to use the word "automated scenario" rather than "acceptance test", which goes back why Dan originally thought of BDD in the first place. You could just use "Automation Glue Code" instead of "Acceptance Test Glue Code".
Other than that, it's a good diagram. I particularly like the emphasis on getting one scenario working at a time! Thank you.
Cheers,Liz.
On Fri, Feb 27, 2015 at 12:49 PM, Stephen Kurlow <sku...@gmail.com> wrote:
I am attempting to produce a diagram that shows:1) 3 Amigos in a workshop preparing Acceptance Criteria for a new Story.2) Turning each acceptance criterion into Acceptance Test Glue Code and Application Code step by step until the complete acceptance test passes for every step3) Once all acceptance criterion have been turned into acceptance test glue code and application code then the story is Done.Obviously other good software engineering practises are being ignored so I'm just focusing on the core BDD process.A couple of questions:1) Can you identify with this process?2) If not how is your process different?3) How can you suggest this diagram be improved? BTW, I'm not the best drawer. :)Thanks,Stephen Kurlow
--
You received this message because you are subscribed to the Google Groups "Behaviour Driven Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendevelopment+unsub...@googlegroups.com.
To post to this group, send email to behaviordriv...@googlegroups.com.
Visit this group at http://groups.google.com/group/behaviordrivendevelopment.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendevelopment+unsub...@googlegroups.com.
To post to this group, send email to behaviordriv...@googlegroups.com.
Visit this group at http://groups.google.com/group/behaviordrivendevelopment.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendeve...@googlegroups.com.
To post to this group, send email to behaviordriv...@googlegroups.com.
Visit this group at http://groups.google.com/group/behaviordrivendevelopment.
For more options, visit https://groups.google.com/d/optout.
I also prefer to use the word "automated scenario" rather than "acceptance test", which goes back why Dan originally thought of BDD in the first place. You could just use "Automation Glue Code" instead of "Acceptance Test Glue Code".I will read the articles you linked soon. Without reading them yet I thought Dan was exploring challenges in teaching TDD to students which is a developer centric activity and then with the help of Chris Matt they explored moving into the requirements/analysis phase so 'it' became more valuable to the whole team from the beginning of a SDLC for developing a story from 'ideas' to Done (consumable in a test/production) env?
--
You received this message because you are subscribed to a topic in the Google Groups "Behaviour Driven Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/behaviordrivendevelopment/Hra7O4fas8Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to behaviordrivendeve...@googlegroups.com.
We started describing the acceptance criteria in terms of scenarios, which took the following form:
Given some initial context (the givens),
When an event occurs,
then ensure some outcomes.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendevelopment+unsub...@googlegroups.com.
To post to this group, send email to behaviordriv...@googlegroups.com.
Visit this group at http://groups.google.com/group/behaviordrivendevelopment.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Behaviour Driven Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendeve...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendevelopment+unsubsc...@googlegroups.com.
To post to this group, send email to behaviordriv...@googlegroups.com.
Visit this group at http://groups.google.com/group/behaviordrivendevelopment.
For more options, visit https://groups.google.com/d/optout.
--You received this message because you are subscribed to the Google Groups "Behaviour Driven Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendevelopment+unsub...@googlegroups.com.
To post to this group, send email to behaviordriv...@googlegroups.com.
Visit this group at http://groups.google.com/group/behaviordrivendevelopment.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to a topic in the Google Groups "Behaviour Driven Development" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/behaviordrivendevelopment/Hra7O4fas8Q/unsubscribe.
To unsubscribe from this group and all its topics, send an email to behaviordrivendevelopment+unsub...@googlegroups.com.
To post to this group, send email to behaviordriv...@googlegroups.com.
Visit this group at http://groups.google.com/group/behaviordrivendevelopment.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Behaviour Driven Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendevelopment+unsub...@googlegroups.com.
To post to this group, send email to behaviordriv...@googlegroups.com.
Visit this group at http://groups.google.com/group/behaviordrivendevelopment.
For more options, visit https://groups.google.com/d/optout.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendevelopment+unsub...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendeve...@googlegroups.com.
To post to this group, send email to behaviordriv...@googlegroups.com.
Visit this group at http://groups.google.com/group/behaviordrivendevelopment.
For more options, visit https://groups.google.com/d/optout.
On 28 Feb 2015, at 21:55, Stephen Kurlow <sku...@gmail.com> wrote:Hi Dan,Thanks for your feedback.The big take away here is to not be hung up on applying the 3 Amigos during the discovery activity? If teams already have another effective discovery method such as any of the ones you mention below then sure continue using it?
To unsubscribe from this group and stop receiving emails from it, send an email to behaviordrivendeve...@googlegroups.com.