{"id":13510,"date":"2017-02-23T00:00:00","date_gmt":"2017-02-23T06:00:00","guid":{"rendered":"https:\/\/centricconsulting.com\/post\/understanding-cucumber-scenarios_sqat\/"},"modified":"2022-01-03T15:22:54","modified_gmt":"2022-01-03T20:22:54","slug":"understanding-cucumber-scenarios_sqat","status":"publish","type":"post","link":"https:\/\/centricconsulting.com\/blog\/understanding-cucumber-scenarios_sqat\/","title":{"rendered":"Understanding Cucumber Scenarios"},"content":{"rendered":"
Blog three of a series<\/a>.<\/em><\/p>\n In the previous blog Understanding Cucumber Features<\/a><\/strong>, we learned where our BDD Acceptance Criteria test scripts need to be placed in the Cucumber automation framework.<\/p>\n But you can\u2019t just copy and paste the script(s) into the .feature file and run them. You need to tell Cucumber that they are scripts. You can accomplish this by using one of three keywords: Scenario, Scenario Outline, or Background.<\/p>\n Scenario Outlines and Backgrounds will be covered in future blogs. Here, we will discuss Scenarios.<\/p>\n The Cucumber Book<\/a> describes each Scenario as \u201c\u2026a single concrete example of how the system should behave in a particular situation. If you add together the behavior defined by all of the scenarios, that\u2019s the expected behavior of the feature itself.\u201d<\/p>\nCucumber Scenarios in Agile Testing Words<\/h2>\n