BDD UND GHERKIN IN DER PRAXIS VON DER ANFORDERUNG ZUR UMSETZUNG

Transkript

1 BDD UND GHERKIN IN DER PRAXIS VON DER ANFORDERUNG ZUR UMSETZUNG CHRISTINE GROEBEL

2 Pilotprojekt: Web Modularisierung EuroWeb EuroVision ModernWeb / 2020 Setup common tech stack for web site development. Use this tech-stack partially already in 2017 business projects. Start migrating outdated systems to new tech stack Define Development guidelines for new platform Define Operating model for new platform Modularisation and migration of outdated systems to new tech-stack Parallel mode of all Websites (EuroWeb / EuroVision / WeMo) New business projects use ModernWeb tech-stack Training of all development teams, support for using new tech-stack Increase automated testing and CI/CD Pilot for BDD in Requirements Engineering Decommission of outdated techstack

3 Warum arbeiten wir mit BDD? Das Projekt Web Modularisierung kämpft mit Anforderungen die nicht dokumentiert wurden. in verschiedenen Formaten dokumentiert wurden. nach der Entwicklung nicht nachdokumentiert wurden. Mit der Verwendung von Behavior Driven Development wollen wir die Kommunikation zwischen Business und IT verbessern. Requirements in einer gemeinsamen Sprache verfassen. Missverständnisse vermeiden statt später Defects zu fixen. Software und Dokumentation erstellen, die wartbar und aktuell bleibt.

4 Was ist BDD? Behavior Driven Development besteht aus drei Kernpraktiken: Discovery Create a shared understanding of the requirements through collaboration, typically achieved through a structured conversation centered on rules and examples. Formulation Examples of system behaviour are documented using business terminology. Automation The documentation is automated, creating living documentation that verifies the system s

5 Was ist Gherkin? Gherkin ist eine menschenlesbare, domainensprezifische Sprache, die entwickelt wurde, um Verhalten von Anwendungen zu beschreiben. In Gherkin geschriebene Anforderungen dienen zwei Zielen: Dokumentation & (automatisiertes) Testen. Formulation Scenarios guide the developer and act as automated tests Discovery PO, Tester & Developer elaborate the requirements and bring them into structured scenarios. Automation The tester uses the Scenarios as basis for their tests PO & Business Find out what the user wants

6 Example Mapping Discovery Formulation Automation

7 Example Mapping Discovery Formulation Automation Kunde hat 100 und kann 20 abheben Kunde hat 20 und kann keine 100 abheben Kunde bekommt Geld, wenn Automat genug Geld enthält Automat enthält 100, Kunde kann 20 abheben Kunde hat 100, hebt 20 ab. Kontostand beträgt jetzt 80.

8 Anforderungen in Gherkin Discovery Feature: Title (one line describing the story) Formulation Narrative: As a [role] I want [feature] so that [benefit] Automation Acceptance Criteria: (presented as Scenarios) Scenario 1: Title Given [context] And [some more context]... When [event] Then [outcome] And [another outcome]... Scenario 2:...

9 Anforderungen in Gherkin Feature: Account Holder withdraws cash Narrative: As an Account Holder I want to withdraw cash from an ATM so that I can get money when the bank is closed. Discovery Formulation Automation Scenario 1: Account has sufficient funds Given the account balance is $100 And the card is valid And the machine contains enough money When the Account Holder requests $20 Then the ATM should dispense $20 And the account balance should be $80 And the card should be returned

10 Anforderungen in Gherkin Discovery Feature: Narrative: Account Holder withdraws cash As an Account Holder I want to withdraw cash from an ATM so that I can get money when the bank is closed Formulation Automation Scenario 1: Account has sufficient funds Given the account balance is \$100 And the card is valid And the machine contains enough money When the Account Holder requests \$20 Then the ATM should dispense \$20 And the account balance should be \$80 And the card should be returned Scenario 2: Account has insufficient funds Given the account balance is \$10 And the card is valid And the machine contains enough money When the Account Holder requests \$20 Then the ATM should not dispense any money And the ATM should say there are insufficient funds And the account balance should be \$20 And the card should be returned Scenario 3: Card has been disabled Given the card is disabled When the Account Holder requests \$20 Then the ATM should retain the card And the ATM should say the card has been retained Scenario xxx:. Given xxx And xxx And xxx When xxx Then xxx And xxx And xxx And xxxx

11 Gherkin in 70 Sprachen

12 Scenarios and now in real life WeMo project space in shary: Development board(s) in JIRA: Flow / UML model etc. GUI / Klickdummy etc. Use Case descripion Requirements Engineering Development Test & Test Automation

13 GDPR / Datenschutzgrundverordnung Re-implementation of GDPR pop-up:

14 Literatur Kamil Nicieja Writing Great Specifications Gaspar Nagy, Seb Rose Discovery: Explore bahviour using examples Jeff Patton User Story Mapping Nutzerbedürfnisse besser verstehen als Schlüssel für erfolgreiche Produkte

15 THANK YOU! BNP PARIBAS 16, rue de Hanovre Paris Tel.: +33 (0) Fax: +33 (0) bnpparibas.com