Lightning talk presented to session #2 of Polymorphic Meetup Paris: https://www.meetup.com/fr-FR/Polymorphic/events/260342370/

1. Can you teach your PO to push
cucumber Gherkins to Git?
Meetic did!

2. Arnaud Georgin
Software Architect
@arnaud_georgin
https://github.com/ageorgin
https://github.com/Meetic

3. Problems to solve
- Implement what is really needed by PO
- Industrialize tests & non regression
- Share the same vocabulary
- Identify and challenge edge cases before development
start
- Improve feedback loop
- One source of truth

4. That’s why we choose
Behaviour-Driven Development Cucumber & Gherkins

5. Goal of Gherkin is: writing features

6. Previous team workflow @ Meetic
Write “legacy”
specifications
present specification during sprint backlog & planning
Write code Write gherkins
store into git repo

7. But...
+
Evangelism, reassure, demonstrate, share, ……, evangelism

8. Step 1/2 : teach Gherkins
- Co-locate PO with dev team
- Install tooling to help PO writing Gherkins (IDE, syntax
highlighter…)
- Pair writing several scenarios with PO (on real use
cases)
- Let PO fail while writing Gherkins
- Refactor with PO

9. Step 1/2 : teach Gherkins
- Implement what is really needed by PO
- Industrialize tests & non regression
- Share the same vocabulary
- Identify and challenge edge cases before development
start
- Improve feedback loop
- One source of truth

10. Step 2/2 : teach git
- Tooling is the key (no CLI for PO)
- Explain git basic features (branches, add, commit)
- Pairing with PO
- Complex operations only made by devs

11. Step 2/2 : teach git
- Implement what is really needed by PO
- Industrialize tests & non regression
- Share the same vocabulary
- Identify and challenge edge cases before development
start
- Improve feedback loop
- One source of truth

12. PO must ….
- store scenarios in the same location as code
- see tests fail and pass on the CI (more implication)
- understand impacts of his changes
- USE GIT !!! create git branch & merge
request for each changes (new
scenario, specification fix)
ask for review
from dev team
rework / adapt
scenarios

13. Questions ?