33927432
Beschreibung
Karteikarten von Charlotte P, aktualisiert more than 1 year ago
|
Erstellt von Charlotte P
vor fast 3 Jahre
|
|
| Frage | Antworten |
| Purpose of Behaviour Driven Development? (BDD) | BDD is used to increase value, decrease waste & increase communication between delivery teams & stakeholders. BDD focuses on the intended behaviour of the customer for the solution to satisfy customer needs. |
| BDD prioritises solutions which deliver value in increments through the use of _____ _________. | 1. real examples |
| BDD uses customer readable, domain specific language to specify the _____ _______ ________ which satisfies the customer need. | intended customer behaviour |
| BAs identify scenarios by asking '______ ___' questions to expose additional scenarios and provide more useful examples. | 'what if' |
| The Gherkin syntax uses a simple syntax of '______ ______ _______'. | |
| BDD examples can be easily converted into ___________ tests, enabling more ____ delivery. | 1. automated 2. agile |
| STRENGTHS of BDD? | - Easy to understand customer needs through simple syntax - 'Given, When, Then' maps to TDD 'Set up, Execute, Assert' pattern - Lends itself towards test automation and test use cases - Scenarios can be easily provided (supports incremental agile nature of projects) - Gherkin syntax can be used to facilitate design discussions to keep focus on intended customer behaviour of a system |
| WEAKNESSES of BDD? | - Possible to miss out important scenarios unless someone is actively asking 'what if' questions - Could be too many scenarios to manage if there are complex business rules - Those maintaining scenarios must been them relevant, current & easy to read |
Möchten Sie mit GoConqr kostenlos Ihre eigenen Karteikarten erstellen? Mehr erfahren.