Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Cucumber Cookbook
  • Table Of Contents Toc
Cucumber Cookbook

Cucumber Cookbook

By : Shankar Garg
3.7 (3)
Buy this Book
close
close
Cucumber Cookbook

Cucumber Cookbook

3.7 (3)
By: Shankar Garg
Buy this Book

Overview of this book

This book is intended for business and development personnel who want to use Cucumber for behavior-driven development and test automation. Readers with some familiarity with Cucumber will find this book of most benefit. Since the main objective of this book is to create test automation frameworks, previous experience in automation will be helpful.
Table of Contents (8 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Sections
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. Writing Feature Files
chevron up
Icon
1. Writing Feature Files
Icon
Introduction
Icon
Writing your first Feature file with one Scenario
Icon
Creating Scenarios with different Steps
Icon
Creating a Scenario with the And and But keywords
Icon
Writing a Feature file with multiple Scenarios
Icon
Adding Backgrounds to Feature files
Icon
Sending multiple arguments in Steps
Icon
Using complex data types to store data
Icon
Implementing Scenario Outlines
Icon
Creating a Feature file in a language other than English
Icon
Combining Scenarios, Backgrounds, and Scenario Outlines
2
2. Creating Step Definitions
Icon
2. Creating Step Definitions
Icon
Introduction
Icon
Creating your first Step Definitions file
Icon
Identifying Duplicate and Ambiguous Step Definitions
Icon
Using Regular Expressions to optimize Step Definitions
Icon
Using Optional Capture and Noncapture Groups
Icon
Transforming Data Tables to parse the test data
Icon
Implementing data table diffs to compare tables
Icon
Using Doc Strings to parse big data as one chunk
Icon
Combining Doc Strings and Scenario Outlines
Icon
Defining String transformations for better conversions
3
3. Enabling Fixtures
Icon
3. Enabling Fixtures
Icon
Introduction
Icon
Tagging
Icon
ANDing and ORing Tags
Icon
Adding Hooks to Cucumber code
Icon
Tagging the Hooks
Icon
ANDing and ORing tagged Hooks
4
4. Configuring Cucumber
Icon
4. Configuring Cucumber
Icon
Introduction
Icon
Integrating Cucumber with JUnit
Icon
Overriding the Cucumber Options
Icon
Running Strict and Running Dry
Icon
Configuring the Cucumber Console output
Icon
Directing the Cucumber output to a file
Icon
Configuring the naming conventions
5
5. Running Cucumber
Icon
5. Running Cucumber
Icon
Introduction
Icon
Integrating Cucumber with Maven
Icon
Running Cucumber from the Terminal
Icon
Overriding Options from the Terminal
Icon
Integrating Cucumber with Jenkins and GitHub
Icon
Running Cucumber test cases in parallel
6
6. Building Cucumber Frameworks
Icon
6. Building Cucumber Frameworks
Icon
Introduction
Icon
Building a Web Automation framework
Icon
Building a Mobile Automation framework
Icon
Building a REST Automation framework
7
Index
Icon
Index

Adding Backgrounds to Feature files

When we write Feature files, we write multiple Scenarios. Now all of these Scenarios start from one particular point. If I'm writing home page Scenarios, then I need to start the flow from the login functionality. So it is better to write the repetitive Steps at one place rather than in all Scenarios. Let's understand how to do this in the next Section.

Getting ready

Based on what we have learned so far, this is what our Feature file will look like:

Feature: Home Page
  In order to test Home Page of application
  As a Registered user
  I want to specify the features of home page

  Scenario: Home Page Default content
    Given a registered user exists
    Given user is on GitHub login page
    When user enters username
    And user enters password
    And user clicks on login button
    Then user is on Application home page
    And user gets a GitHub bootcamp section

  Scenario: GitHub Bootcamp Section
    Given user is on GitHub loginpage
    When user enters username
    And user enters password
    And user clicks on login button
    Then user is on Application home page
    When user focuses on GitHub Bootcamp Section
    Then user gets an option to setup git

  Scenario: Top Banner content
    Given user is on GitHub login page
    When user enters username
    And user enters password
    And user clicks on login button
    Then user is on Application home page
    When user focuses on Top Banner
    Then user gets a logout option

The problem here is that first five statements are repeated in all the Scenarios. This affects the readability of the Feature files, and there is a lot of duplicated effort.

The problems with this way of writing Feature files are:

  • Repetition: Many statements are repeated in all the Scenarios
  • Readability: The readability of the Feature files is affected.
  • Duplication: Copying these Steps to all the Scenarios is redundant.
  • Maintainability: Even if a single Step changes, we have to change all occurrences.

How to do it…

We are going to update the home_page.feature file and we are going to use the Background keyword to put the common Steps across all the Scenarios in one place:

Feature: Home Page
  In order to test Home Page of application
  As a Registered user
  I want to specify the features of home page

  Background: flow till home page
    Given user is on Application home page
    When user enters username
    And user enters password
    And user clicks on login button
    Then user is on Application home page

  Scenario: Home Page Default content
    Then user gets a GitHub bootcamp section

  Scenario: GitHub Bootcamp Section
    When user focuses on GitHub Bootcamp Section
    Then user gets an option to setup git

  Scenario: Top Banner content
    When user focuses on Top Banner
    Then user gets an option of home page

How it works…

Here, we have used the Background keyword. All the Steps mentioned in the Background keyword will be executed before each Scenario or Scenario Outline in a Feature file. Let's understand this keyword in greater detail:

  • There can be only one Background in one Feature file and it allows us to set a precondition for all Scenarios in a Feature file.
  • A Background is like a Scenario, containing a number of Steps.
  • Background is run before each Scenario, but after the BeforeScenario Hooks. (We will read about Hooks in Chapter 3, Enabling Fixtures).
  • The title and multiline description / intent of Background are optional.
  • Since the Steps mentioned in Background will be run for all Scenarios in a Feature file, we need to be careful when adding the Steps to Background. For example, we should not add a Step that is not common to all Scenarios.

This is what the output of the preceding file looks like:

How it works…

Don't use Background to set up a complicated state unless that state is actually something the client needs to know.

  • Keep your Background section short because you expect a person to remember these Steps when you are adding a new Scenario
  • Make your Background section vivid, because that way it will be easier for a person to remember it
CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Cucumber Cookbook
End of Section 1
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon