Now that your Cucumber project has been created<\/a> <\/span>and Gherkin scripts are in hand, your agile testing team is ready to automate. <\/span><\/p>\n But, before we jump into coding, a few concepts need to be explained. <\/span><\/p>\n The first concept is <\/span>Features<\/b>. Other concepts – <\/span>Scenarios<\/b><\/a>, <\/span>Gherkin<\/b> scripting<\/span>, and <\/span>WebDriver –\u00a0<\/b>will be discussed in future blog entries<\/a>.<\/span><\/p>\n Depending on which agile tool you use or which agile book you read, user stories are sometimes referred to as a Feature. For us, they are one and the same. Both describe, from a user point of view, a requirement the business is requesting. <\/span><\/p>\n Authors of <\/span>The Cucumber Book<\/span><\/i><\/a>\u00a0define Features as groups of tests, stating \u201c\u2026we want them to describe the features that a user will be able to enjoy when using our program.\u201d<\/span><\/p>\n That is a pretty good definition since we are going to be placing our Acceptance Script(s) in the Feature file along with any additional test cases we come up with. Each Feature is placed in a .feature file that resides in the project\/features directory.<\/span><\/p>\n To create a .feature file in Cucumber:<\/span><\/p>\n This will create a .feature file in the Features directory:<\/span><\/p>\n There are a couple of things every agile testing team should notice:<\/span><\/p>\n To finish this lesson, we need to add a title to our .feature file. <\/span><\/p>\n Put your cursor on the first line of the .feature file and type: \u201cFeature: <User Story title>\u201d. It will look like this:<\/span><\/p>\nCreating a File in Cucumber Features Directory<\/h2>\n
\n
![\"Cucumber](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2018\/07\/Blog-2-Image-1.png\")
<\/a><\/p>\n\n
Adding a Title\u00a0in Feature File<\/h2>\n
![\"Cucumber](\"https:\/\/centricconsulting.com\/wp-content\/uploads\/2018\/07\/Blog-2-Image-2.png\")
<\/a><\/p>\n