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

Combining Scenarios, Backgrounds, and Scenario Outlines

Until now we have learned about Scenarios, Steps, Background, and Scenario Outline individually. But when a BA or a PO has to write the Feature file, they have to combine all these keywords to come up with a very efficient and expressive Feature file.

Consider writing a Feature file for a login functionality where the latter meets the following criteria:

  • The user should get an option to log in from the application's home page
  • To log in, a user should have a username and password
  • After a successful login, the user should be redirected to the home page
  • In case of an unsuccessful login, the user should get the appropriate message
  • The user should also get an option to register new users on the home page
  • The user should also be able to verify which users exist in the application (this Feature is not present on the GitHub landing page but has been added for to clarify concepts)

    Note

    All these requirements are specific to the behavior of the application, and none of them are concerned with how you implement these requirements.

How to do it…

Now we are going to use all the keywords we have explored until now, and we are going to create a login.feature file that specifies all the aforementioned requirements:

Feature: login Page
  In order to test login page
  As a Registered user
  I want to specify the login conditions

  Scenario: login flow
    Given user is on Application landing page
    And Sign in button is present on screen
    When user clicks on Sign in button
    Then user is displayed login screen
    When user enters "ShankarGarg" in username field
    And user enters "123456" in password field
    And user clicks Sign in button
    Then user is on home page
    And title of home page is "GitHub"

  Scenario Outline: Login fail - possible combinations
    Given user is on Application landing page
    When user clicks on Sign in button
    Then user is displayed login screen
    When user enters "<UserName>" in username field
    And user enters "<Password>" in password field
    And user clicks Sign in button
    Then user gets login failed error message

    Examples: 
      | UserName      | Password      |
      | wrongusername | 123456        |
      | ShankarGarg   | wrongpassword |
      | wrongusername | wrongpassword |

  Scenario: Existing user Verification
    Given user is on Application landing page
    Then we verify following user exists
      | Name    | Email           | Phone |
      | Shankar | [email protected] | 999   |
      | Ram     | [email protected]   | 888   |
      | Sham    | [email protected]  | 666   |

  Scenario: New User Registration
    Given user is on Application landing page
    When user enters "ShankarGarg" in username field
    And user enters "[email protected]" in password field
    And user enters "123456" in password field
    And user clicks on Signup for GitHub button
    Then user is successfully registered

How it works…

Here we have combined all the keywords and concepts discussed until now in this chapter. Let's go through each requirement one by one and analyze how and with which keyword we specified these requirements:

  • User should get an option to log in from the application home page—Scenario
  • For login, a user should have a username and password—Scenario
  • After successful login, the user should be redirected to the home page—Scenario
  • In case of unsuccessful login, the user should get the appropriate message—Scenario Outline
  • The user should also get an option to register new users on the home page—Scenario
  • The user should also be able to verify which users exist in the application—Data Table
Visually different images
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 Chapter 1
Next Chapter
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