Make Your Automation Behave: Extending Your Framework for BDD – Angie Jones
post-template-default,single,single-post,postid-4169,single-format-standard,eltd-core-1.1.1,flow-ver-1.3.7,,eltd-smooth-page-transitions,ajax,eltd-grid-1300,eltd-blog-installed,page-template-blog-standard,eltd-header-vertical,eltd-sticky-header-on-scroll-up,eltd-default-mobile-header,eltd-sticky-up-mobile-header,eltd-dropdown-default,wpb-js-composer js-comp-ver-5.0.1,vc_responsive

Make Your Automation Behave: Extending Your Framework for BDD

Make Your Automation Behave: Extending Your Framework for BDD

When done properly, Behavior-Driven Development (BDD) can drastically improve the communication and understanding of requirements. An additional benefit is being able to utilize the domain-specific language of the requirements to drive test automation. However, like any other automation initiative, when done poorly, this too can fail.

In the session below, I provide a hands-on technical look into how to:

  • utilize Gherkin-written scenarios for test automation
  • write scenarios in a way that promote maintainability and reusability
  • take advantage of advanced Gherkin functionality such as data tables and objects
  • tie the scenarios to automation code
  • incorporate this approach into existing automation frameworks that use the page object model design pattern
  • share state across multiple steps within a scenario


Upon completion of this session, you’ll have a better understanding of how to

  • Enhance your BDD initiative with test automation
  • Cleanly extend an automation framework to support executable requirement specifications
  • Support advanced techniques such as data tables and objects within specifications, as well as sharing state through dependency injection.



Angie Jones
1 Comment

Post a Comment