Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Joy of 
automated acceptance tests with Cucumber

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.

62b3ae0dcd8e12a5eedd1fbe417bc6c8?s=128

Marit van Dijk

June 08, 2018
Tweet

Transcript

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

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

  3. Specification (Gherkin) @MaritvanDijk77

  4. Step definitions @MaritvanDijk77

  5. Expected benefits + Easy to communicate + Automated verification @MaritvanDijk77

    * actual commit message ;)
  6. Unexpected benefits + Reusable steps + Identify missing information +

    Up-to-date documentation! @MaritvanDijk77
  7. Layers Feature file Helpers StepDefs Application Expected behavior - Natural

    language “Glue” Reusable test code Programming language @MaritvanDijk77
  8. When not to use it? •Benefits < cost •Communication @MaritvanDijk77

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