Joy of automated acceptance tests with Cucumber

Joining a Scrum team as the first tester was challenging, since I’m not a ‘traditional’ tester. My test experience is in automation, while the team was expecting manual regression testing.

Early on, I introduced Cucumber; a Behaviour Driven Development (BDD) tool to automate acceptance tests.

This talk will highlight the intended - and unintended - benefits using Cucumber has brought to my team. You will learn what Cucumber could do for you, and when not to use it.

Transcript

1. @MaritvanDijk77
   github.com/mlvandijk
   medium.com/@mlvandijk
   Joy of
   automated acceptance tests
   with Cucumber
   

   View Slide

2. Why Cucumber?
   •Natural language specification
   •Automated tests
   @MaritvanDijk77
   

   View Slide

3. Specification (Gherkin)
   @MaritvanDijk77
   

   View Slide

4. Step definitions
   @MaritvanDijk77
   

   View Slide

5. Expected benefits
   + Easy to communicate
   + Automated verification
   @MaritvanDijk77
   * actual commit message ;)
   

   View Slide

6. Unexpected benefits
   + Reusable steps
   + Identify missing information
   + Up-to-date documentation!
   @MaritvanDijk77
   

   View Slide

7. Layers
   Feature file
   Helpers
   StepDefs
   Application
   Expected behavior - Natural language
   “Glue”
   Reusable test code
   Programming
   language
   @MaritvanDijk77
   

   View Slide

8. When not to use it?
   •Benefits < cost
   •Communication
   @MaritvanDijk77
   

   View Slide

9. @MaritvanDijk77
   github.com/mlvandijk
   medium.com/@mlvandijk
   Joy of
   automated acceptance tests
   with Cucumber
   

   View Slide