BDD

vibssingh

Cucumber Multiple Choice Answers – MCQ2

Last Updated On

HOME

Are you familiar with Cucumber and want to test your understanding? This post contains 25 useful Cucumber multiple-choice questions (quiz) to self-test your knowledge of Cucumber.

You can find the questions for the below-mentioned answers in this post –

Cucumber Quiz: 25 Multiple-Choice Questions with Answers – MCQ2

Answers

1) 4) All of the above

2) 1) Gherkin

3) 3) A table of input parameters

4) 2) Scenario Outline: Login with invalid credentials

5) 2) dryRun

6) 4) –glue

7) 2) –strict

8) 1) mvn test -Dcucumber.filter.tags=”@regression”

9) 1) mvn test -Dcucumber.features=”src/test/resources/features/Login.feature”

10) 3) mvn test -Dcucumber.glue=”com.example.stepdefinitions”

11) 1) mvn test -Dcucumber.plugin=”html:target/cucumber-reports/cucumberReport.html”

12) 1) True

13) 1) True

14) 2) Feature

15) 1) 

mvn test -Dcucumber.features="src/test/resources/LoginPage.feature" -Dcucumber.filter.tags="@ValidCredentials"

16) 1) @CucumberOptions

17) 3)

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
import org.junit.runner.RunWith;
 
@RunWith(Cucumber.class)
@CucumberOptions(plugin = {"pretty"})
public class RunCucumberTest {
}

18) 1) Yes

19) 1) monochrome=true

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
import org.junit.runner.RunWith;
 
@RunWith(Cucumber.class)
@CucumberOptions(monochrome=true)
public class RunCucumberTest {
}

20) 4) Run the scenario tagged with both smoke and regression

21) 4) All of the above

22) 1) Yes

23) 1) Yes

24) 1) Yes

25) 1) Yes. It is the Test Runner using TestNG.

vibssingh

BDD Multiple Choice Questions – MCQ1

Last Updated On

HOME

BDD Quiz – You can test your knowledge with this BDD Quiz. We have created this Behaviour Driven Development Quiz Online Test to help you master BDD.

1. What is the full form of BDD?

Select the best answer

  1. Behavior Driven Development
  2. Behind Driven Development
  3. Behavior Data Development
  4. Behavior Driven Database

Answer

2. ___is a software development technique where automated tests are written before the code

Choose one option

  1. TDD
  2. BDD
  3. ATDD
  4. None

Answer

3. ___is a process of developing software based on behavioural specification of software units.

Choose one option

  1. TDD
  2. BDD
  3. ATDD
  4. None

Answer

4. What are the 3 Practices of BDD?

Choose one option

  1. Discovery, Integration, Development
  2. Discovery, Formulation, Development
  3. Discovery, Formulation, Automation

Answer

5. What is the sequence of the 3 Practices of BDD?

Choose one option

  1. Discovery, Automation, Formulation
  2. Discovery, Formulation, Automation
  3. Formulation, Discovery, Automation

Answer

6. What is the outcome of the Discovery phase?

  1. Common agreed understanding of the behaviour of the system
  2. Documented Examples
  3. All
  4. None

Answer

7. What is the outcome of the Formulation phase

  1. Common agreed understanding of the behaviour of the system
  2. Documented Examples
  3. All
  4. None

Answer

8. What is the outcome of the Automation phase?

Choose one option

  1. Implemented Code + Automation Tests
  2. Written Documentation of Examples
  3. Common agreed understanding of the behaviour of the system
  4. None

Answer

9. Why we call the Discovery meeting as the “3 Amigos meeting“

Choose one option

  1. Only 3 people should attend this meeting
  2. Minimum 3 people should attend
  3. To have a different perspective from at least 3 different teams to discuss and create a common understanding
  4. None

Answer

10. Who are the “3 Amigos”?

Choose one option

  1. Top 3 developers of the team
  2. Top 3 testers of the team
  3. Product Owner, Developer & Tester
  4. None

Answer

11. What is a USER STORY?

Choose one options

  1. A story about a user
  2. General description of the software feature or change from an end-user perspective
  3. It outlines software architecture and design
  4. None

Answer

12.  Who writes a USER STORY

Choose one option

  1. Product Owner
  2. Developer
  3. Tester
  4. Program Manager

Answer

13. What is/are the characteristic(s) of BDD?

Choose one option

  1. Strong Collaboration
  2. High Visibility
  3. Lower Costs
  4. All of the above

Answer

14. What are some benefits of automating tests in BDD?

Choose one option

  1. Increased Test Coverage
  2. Continuous Integration/Continuous Delivery (CI/CD) Support
  3. Improved Collaboration
  4. All of the above

Answer

15. What is Cucumber

Choose one option

  1. A tool to facilitate BDD
  2. Helps in converting documented examples to automation tests
  3. All of the above

Answer

16. what are the challenges of automation in BDD?

Choose one option

  1. Maintenance Overhead
  2. Initial Setup and Learning Curve
  3. Both (1) and (2)
  4. None

Answer

17. Using Cucumber means you are doing BDD

Choose one option

  1. False
  2. True
  3. None

Answer

18. Which of the following are BDD Tools?

Choose correct options

  1. Selenium
  2. Cucumber
  3. Serenity
  4. None

Answer

 19. What are the advantages of Cucumber?

  1. Cucumber acceptance tests are written from user’s the perspective.
  2. Team Collaboration (Product owners, business analysts, developers, testers are all involved in writing scenarios)
  3. Tests are written in plain-text English, so people with less technical skills can also write scenarios.
  4. All of the above

Answer

20. Which was the original programming language used to create the Cucumber tool.

Choose one option

  1. Java
  2. C++
  3. C
  4. Ruby

Answer

====================================================================

Answers

1) 1) Behavior Driven Development
2) 2) TDD
3) 2) BDD
4) 3) Discovery, Formulation, Automation
5) 2) Discovery, Formulation, Automation
6) 1) Common agreed understanding of the behaviour of the system
7) 2) Documented Examples
8) 1) Implemented Code + Automation Tests
9) 3) To have a different perspective from at least 3 different teams to discuss and create a common understanding
10) 3) Product Owner, Developer & Tester
11) 2) General description of the software feature or change from an end-user perspective
12) 1) Product Owner
13) 4) All of the above
14) 4) All of the above
15) 3) All of the above
16) 3) Both (1) and (2)
17) 1) False
18) 2) Cucumber and 3) Serenity
19) 4) All of the above
20) 4) Ruby

Selenium Multiple Choice Questions – MCQ1

Selenium Multiple Choice Questions – MCQ2

vibssingh

Cucumber Quiz: 25 Multiple-Choice Questions with Answers – MCQ2

Last Updated On

HOME

Are you familiar with Cucumber and want to test your understanding? This post contains 25 useful Cucumber multiple-choice questions (quiz) to self-test your knowledge of Cucumber.

Cucumber Multiple Choice Questions – MCQ1

1. What is the purpose of Cucumber?

Select the best answer

  1. To write tests in a human-readable format
  2. To automate software testing
  3. To improve software quality
  4. All of the above

Answer

2. The __ programming language is used for the creation of these executable test scripts.

Choose one option

  1. Gherkin
  2. Gerkin
  3. Gerin
  4. Gerkn

Answer

3. Which of the following is an example of a Cucumber data table?

Choose one option

  1. A table of test results
  2. A table of test requirements
  3. A table of input parameters
  4. A table of test scenarios

Answer

4. Which of the following is an example of a Cucumber scenario outline?

Choose one option

  1. Scenario: Login with valid credentials
  2. Scenario Outline: Login with invalid credentials
  3. scenario: Add item to shopping cart
  4. scenario outline: Search for product

Answer

5.  Which option check if all the steps have the step definition before execute?

Choose one option

  1. monochrome
  2. dryRun
  3. strict
  4. validate

Answer

6.  Which of the following is a Cucumber option that can be used to specify the path to the feature files?

  1. –tags
  2. –strict
  3. –format
  4. –glue

Answer

7. Which of the following is a Cucumber option that can be used to enforce stricter syntax checking?

  1. –tags
  2. –strict
  3. –name
  4. –format

Answer

8. Which of the following is a Maven command that can be used to run scenarios that have been tagged as “regression” tests in Cucumber?

mvn test -Dcucumber.filter.tags="@regression"

mvn test -Dcucumber.tags="@regression"

mvn test -cucumber.filter.tags="@regression"

Answer

9. Which of the following is a Maven command that can be used to run a feature file in Cucumber

Choose one option

mvn test -Dcucumber.features="src/test/resources/features/Login.feature"

mvn test -Dcucumber.features="src/test/resources/features/Login"

mvn test -cucumber.feature="src/test/resources/features/Login.feature"

Answer

10. Which of the following is a Maven command that can be used to pass the glue code in Cucumber

Choose one option

mvn test -Dcucumber.gluecode="com.example.stepdefinitions"

mvn test -Dcucumber.glue_code="com.example.stepdefinitions"

mvn test -Dcucumber.glue="com.example.stepdefinitions"

Answer

11. Which of the following is a Maven command that can be used to generate Cucumber Report

Choose one option

mvn test -Dcucumber.plugin="html:target/cucumber-reports/cucumberReport.html"

mvn test -cucumber.plugin="html:target/cucumber-reports/cucumberReport.html"

mvn test -Dcucumber.plugins="target/cucumber-reports/cucumberReport"

Answer

12.  Tags that are placed above a Scenario Outline will be inherited by Examples

Choose one option

  1. True
  2. False

Answer

13. Below is a valid example of Scenario Outline

Scenario Outline: Login to Home Page
  Given user is logged in
  When user clicks <link>
  Then user will be logged out

  @mobile
  Examples:
    | link                   |
    |  mobile logout |

  @desktop
  Examples:
    | link                    |
    | desktop logout |

Choose one option

  1. True
  2. False

Answer

14.  Tags that are placed above a __ will be inherited by Scenario, Scenario Outline, or Examples.

Choose one option

  1. Scenario Outline
  2. Feature
  3. Background
  4. None

Answer

15. Select a valid example of running multiple parameters in the Cucumber

mvn test -Dcucumber.features="src/test/resources/LoginPage.feature" -Dcucumber.filter.tags="@ValidCredentials"

mvn test -Dcucumber.features="src/test/resources/LoginPage.feature" and -Dcucumber.filter.tags="@ValidCredentials"

mvn test -Dcucumber.features="src/test/resources/LoginPage.feature" or -Dcucumber.filter.tags="@ValidCredentials"

Answer

16. The __ can be used to provide additional configuration to the runner.

Choose one option

  1. @CucumberOptions
  2. @Cucumber
  3. @Options
  4. None

Answer

17. Which of the following is an example of Cucumber TestRunner?

import io.cucumber.junit.CucumberOptions;
import org.junit.runner.RunWith;

@RunWith
@CucumberOptions(plugin = {"pretty"})
public class RunCucumberTest {
}

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;

@CucumberOptions(plugin = {"pretty"})
public class RunCucumberTest {
}

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
import org.junit.runner.RunWith;

@RunWith(Cucumber.class)
@CucumberOptions(plugin = {"pretty"})
public class RunCucumberTest {
}

Answer

18. Can we run the tests in Cucumber parallelly?

Choose one option

  1. Yes
  2. No

Answer

 19. How to print console output from Cucumber in a readable format?

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
import org.junit.runner.RunWith;

@RunWith(Cucumber.class)
@CucumberOptions(monochrome=true)
public class RunCucumberTest {
}

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
import org.junit.runner.RunWith;

@RunWith(Cucumber.class)
@CucumberOptions(plugin = {"pretty", "summary"})
public class RunCucumberTest {
}

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
import org.junit.runner.RunWith;

@RunWith(Cucumber.class)
@CucumberOptions(snippets = SnippetType.CAMELCASE)
public class RunCucumberTest {
}

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
import org.junit.runner.RunWith;

@RunWith(Cucumber.class)
@CucumberOptions(dryRun=true)
public class RunCucumberTest {
}

Answer

20. Which of the following is an example of a Cucumber plugin?

mvn test -Dcucumber.tags="@smoke and @regression"

Choose one option

  1. Run all the scenarios in the feature file
  2. Run the scenario tagged with smoke
  3. Run the scenario tagged with regression
  4. Run the scenario tagged with both smoke and regression

Answer

21. What are the different types of hooks

Choose one option

  1. Scenario Hook
  2. Step Hook
  3. Conditional Hook
  4. All of the above

Answer

22. Can we integrate Cucumber with TestNG?

Choose one option

  1. Yes
  2. No

Answer

23. Can we integrate Cucumber with JUnit?

Choose one option

  1. Yes
  2. No

Answer

24. Can we execute the Cucumber tests in CI/CD like GitHub pipeline, Jenkins and so

Choose one option

  1. Yes
  2. No

Answer

25. Below is the valid syntax for the Test Runner class?

import io.cucumber.testng.AbstractTestNGCucumberTests;
import io.cucumber.testng.CucumberOptions;
 
@CucumberOptions(features = "src/test/resources/Features")
 public class CucumberRunnerTests extends AbstractTestNGCucumberTests {
 
}

Choose one option

  1. Yes
  2. No

Answer

====================================================================

vibssingh

Cucumber Multiple Choice Answers – MCQ1

Last Updated On

HOME

Are you familiar with Cucumber and want to test your understanding? This post contains 25 useful Cucumber multiple-choice questions (quiz) to self-test your knowledge of Cucumber.

You can find the questions for the below-mentioned answers in this post –

Cucumber Multiple Choice Questions – MCQ1

Answers

1) 2) BDD (Behaviour driven development)

2) 4) All of the above

3) 3) Gherkin

4) 1) Describe the scenarios, behaviour, and expected result of a feature.

5) 2) It is an interface between a feature file and a step definition file, and it is used to execute the step definition file corresponding to a feature file.

6) 1) It is a Java method with an expression that links it to one or more Gherkin steps. When Cucumber executes a Gherkin statement in a scenario, it will look for a matching step definition to execute.

7) 4) .feature

8) 1) Background 4) Scenario Outline 5) Feature 6) Given 8) When

9) 1) Feature

10) 1) Given

11) 2) When

12) 1) Then

13) 2) But

14) 1) And

15) 3) Background

16) 1) A way to run the same scenario with different inputs

17) 1) A piece of code that runs before or after a scenario or feature

18) 1) A label that can be applied to a scenario or feature

19) 1) To describe the setup, action, and expected result of a scenario

20) 1) Cucumber Reports

21) 4) All of the above

22) 1) @

23) 3) Both 1 and 2

24) 1) ~

25) 2) If

vibssingh

Cucumber Multiple Choice Questions – MCQ1

Last Updated On

HOME

Are you familiar with Cucumber and want to test your understanding? This post contains 25 useful Cucumber multiple-choice questions (quiz) to self-test your knowledge of Cucumber.

1. Cucumber is based on which framework?

Select the best answer

  1.  TDD (Test driven development)
  2.  BDD (Behaviour driven development)
  3.  MVC (Model view controller)
  4. None

Answer

2. What is/are the advantage(s) of the Cucumber Tool?

Choose one option

  1. Cucumber Testing focuses primarily on the end-user experience since the end-user experience ultimately determines the success of software.
  2. There is no difficulty in writing test cases.
  3. In contrast to other tools, it provides a framework for testing an entire application.
  4. All of the above

Answer

3. Which of the below languages is used in Cucumber to describe the scenarios, behavior, and expected result of a feature?

Choose one option

  1.  Python
  2.  Ruby
  3.  Gherkin
  4. Java

Answer

4. A feature file in cucumber is used to __

Choose one option

  1. Describe the scenarios, behaviour, and expected result of a feature.
  2. Create the test code in StepDefinition.
  3. Both (1) and (2)
  4. None of the above

Answer

5.  Which of the following is true for a TestRunner class in cucumber?

Choose one option

  1. It is a Java file that defines or implements the logic for the scenario defined in the feature file.
  2. It is an interface between a feature file and a step definition file, and it is used to execute the step definition file corresponding to a feature file.
  3. Describe the scenarios, behaviour, and expected result of a feature.
  4. None

Answer

6.  Which of the following is true for the Step Definition in cucumber?

  1. It is a Java method with an expression that links it to one or more Gherkin steps. When Cucumber executes a Gherkin statement in a scenario, it will look for a matching step definition to execute.
  2. It is a Java file that is used to trigger the TestRunner class.
  3. Describe the scenarios, behaviour, and expected result of a feature.
  4. None

Answer

7. Files with the extension __ are feature files.

  1. .f
  2. .fea
  3. .feat
  4. .feature

Answer

8. Select all the valid Gherkin keywords that can be used in a feature file to define the application behaviour:

  1.  Background
  2.  void
  3.  super
  4.  Scenario Outline
  5.  Feature
  6.  Given
  7.  this
  8.  When

Answer

9. There is a __ keyword at the beginning of every Cucumber testing feature file.

Choose one option

  1. Feature
  2. Scenario
  3. Then
  4. When

Answer

10. The preconditions of a test are described by the __ keyword.

Choose one option

  1. Given
  2. When
  3. Then
  4. Feature

Answer

11. A user’s actions are normally executed when they are defined as ___.

Choose one option

  1. Then
  2. When
  3. For
  4. Given

Answer

12.  A keyword called ‘___’ pertains to what happens after a previous step or action

Choose one option

  1. Then
  2. When
  3. Given
  4. But

Answer

13. Negative conditions are added with the ‘___’ keyword.

Choose one option

  1. Background
  2. But
  3. And
  4. Or

Answer

14.  When you add conditions to your steps, you use the ‘___’ keyword.

Choose one option

  1. And
  2. But
  3. Background
  4. For

Answer

15. Tests in a feature file use the ‘___’ keyword to define common steps.

Choose one option

  1. Back
  2. Ground
  3. Background
  4. For

Answer

16. What is a scenario outline in Cucumber?

Choose one option

  1. A way to run the same scenario with different inputs
  2. A way to run multiple scenarios in parallel
  3. A way to define the requirements for a particular feature
  4. A way to define the test results for a particular feature

Answer

17. What is a hook in Cucumber?

Choose one option

  1. A piece of code that runs before or after a scenario or feature
  2. A file that contains the test scenarios for a particular feature
  3. A file that contains the requirements for a particular feature
  4. A file that contains the test results for a particular feature

Answer

18. What is a tag in Cucumber?

Choose one option

  1. A label that can be applied to a scenario or feature
  2. A way to run multiple scenarios in parallel
  3. A way to define the requirements for a particular feature
  4. A way to define the test results for a particular feature

Answer

 19. What is the purpose of the Given-When-Then syntax in Gherkin?

  1. To describe the setup, action, and expected result of a scenario
  2. To define the requirements for a particular feature
  3. To define the test results for a particular feature
  4. To run the same scenario with different inputs

Answer

20. Which of the following is an example of a Cucumber plugin?

Choose one option

  1. Cucumber Reports
  2. JUnit
  3. Selenium
  4. TestNG

Answer

21. Which of the following is an example of a Cucumber tag expression?

Choose one option

  1. @smoke
  2. @smoke or @regression
  3. @smoke and @regression
  4. All of the above

Answer

22. Tags are declared using the __ symbol

Choose one option

  1. @
  2. #
  3. $
  4. &

Answer

23.  Operators can be used to test multiple tags:

Choose one option

  1. OR operator
  2. AND operator
  3. Both 1 and 2
  4. None of the above

Answer

24. In order to skip the test, a special symbol __ can be used within the tag.

Choose one option

  1. ~
  2. /
  3. \
  4. !

Answer

25. Which of the following keywords is NOT used while writing the Cucumber scenario?

Choose all options

  1. Given
  2. If
  3. But
  4. Then

Answer

====================================================================

Answers

1) 2) BDD (Behaviour driven development)
2) 4) All of the above
3) 3) Gherkin
4) 1) Describe the scenarios, behaviour, and expected result of a feature.
5) 2) It is an interface between a feature file and a step definition file, and it is used to execute the step definition file corresponding to a feature file.
6) 1) It is a Java method with an expression that links it to one or more Gherkin steps. When Cucumber executes a Gherkin statement in a scenario, it will look for a matching step definition to execute.
7) 4) .feature
8) 1) Background 4) Scenario Outline 5) Feature 6) Given 8) When
9) 1) Feature
10) 1) Given
11) 2) When
12) 1) Then
13) 2) But
14) 1) And
15) 3) Background
16) 1) A way to run the same scenario with different inputs
17) 1) A piece of code that runs before or after a scenario or feature
18) 1) A label that can be applied to a scenario or feature
19) 1) To describe the setup, action, and expected result of a scenario
20) 1) Cucumber Reports
21) 4) All of the above
22) 1) @
23) 3) Both 1 and 2
24) 1) ~
25) 2) If

vibssingh

Multiple Choice Questions

Last Updated On

HOME

Selenium

Selenium Multiple Choice Questions – MCQ1
Selenium Multiple Choice Questions – MCQ2
Selenium Multiple Choice Answers – MCQ3

Rest API

Rest API Multiple Choice Questions – MCQ1 – NEW
Rest API Multiple Choice Questions – MCQ2 – NEW

TestNG

TestNG Multiple Choice Questions – MCQ1 – Coming Soon
TestNG Multiple Choice Questions – MCQ2 – Coming Soon

Cucumber

BDD Multiple Choice Questions – MCQ1 – NEW
Cucumber Multiple Choice Questions – MCQ1 – New
Cucumber Quiz: 25 Multiple-Choice Questions with Answers – MCQ2 – NEW
vibssingh

Tags in Cucumber

Last Updated On

HOME

In this tutorial, I will explain Tags in Cucumber.

Table of Contents

  1. What are Tags?
    1. Running a single Cucumber Tag
    2. How to execute Cucumber Tag that runs multiple scenarios
    3. How to execute Multiple Cucumber Tags
      1. OR operator
      2. AND operator
    4. How to ignore Tags in Cucumber?
    5. How to run multiple feature files

What are Tags?

Tags are a great way to organize Features and Scenarios.
By default, Cucumber executes all the scenarios present in a Feature File. If you want to run a specific scenario from the feature file, then a tag can be used.

Tags can be declared as below:-

@TagName
   Scenario: Test the scenario

Here,

@: It is a symbol used to declare a tag.
TagName: It is the name of a specific test.

In the below example, there are 2 feature files – LoginPage.feature and DashboardPage.feature. LoginPage.feature contains 4 different scenarios with different tags, whereas DashboardPage.feature contains 3 different scenarios.

LoginPage.feature

Feature: Login to HRM Application

  Background:
    Given User is on Login page

  @ValidCredentials
  Scenario: Login with valid credentials

    When User enters username as "Admin"
    And User enters password as "admin123"
    Then User should be able to login successfully

  @InValidCredentials
  Scenario: Login with invalid credentials

    When User enters username as "Admin123"
    And User enters password as "admin123"
    Then User should see an error message "Invalid credentials"

  @InValidCredentials
  Scenario: Login with invalid username and valid password

    When User enters username as "1234"
    And User enters password as "admin123"
    Then User should see an error message "Invalid credentials"

  @InValidCredentials @SpecialCharacters
  Scenario: Login with special characters

    When User enters username as "$$$$"
    And User enters password as "%%%%%"
    Then User should see an error message "Invalid credentials"

DashboardPage.feature

Feature: Dashboard page validation

  Background:
    Given User is on Login page
    When User enters username as "Admin"
    And User enters password as "admin123"
    Then User should be able to login successfully

  @ValidQuickLaunch
  Scenario Outline: Login with valid credentials to check QuickLanuch options

    Then there are valid QuickLaunch options '<options>'

    Examples:
      | options                  |
      | Assign Leave             |
      | Leave List               |
      | Timesheets               |

Running a single Cucumber Tag

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
import org.junit.runner.RunWith;

@RunWith(Cucumber.class)
@CucumberOptions(features= {"src/test/resources/features"}, glue= {"org.example.definitions"},
        tags = ("@ValidCredentials"))

public class RunCucumberTest {
}

In the above example, only 1 scenario is tagged as @ValidCredentials in both the feature file, so it is executed.

The output of the above program is

Tags can be placed above Feature, Scenario, Scenario Outline, and Examples.

A feature or Scenario can have as many tags. However, each tag should be separated by a blank space.

How to execute Cucumber Tag that runs multiple scenarios

Let us consider a situation where a tag (@InValidCredentials) has multiple test scenarios, and you use this tag in the Runner class, then all the test scenarios associated with this tag will execute.

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
import org.junit.runner.RunWith;

@RunWith(Cucumber.class)
@CucumberOptions(features= {"src/test/resources/features"}, glue= {"org.example.definitions"},
        tags = ("@InValidCredentials"))

public class RunCucumberTest {
}

The output of the above program is

How to execute Multiple Cucumber Tags

The testing through multiple tags can be done by using two operators:

  1. OR operator
  2. AND operator

OR operator

OR means scenarios that are tagged either with @BlankCredentials or @InvalidCredentials will execute. The syntax is mentioned below:

import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
import org.junit.runner.RunWith;

@RunWith(Cucumber.class)
@CucumberOptions(features= {"src/test/resources/features"}, glue= {"org.example.definitions"},
        tags = ("@ValidCredentials or @SpecialCharacters"))

public class RunCucumberTest {
}

In the above example, we have 1 scenario that is tagged as @ValidCredentials and another one tagged as @SpecialCharacters. So, a total of 2 scenarios are executed.

The output of the above program is

AND operator

Suppose you want to test an application with multiple test cases and if the first test case is failed in the application, we do not want to test the second test case. The syntax is mentioned below:

@CucumberOptions(features = { "src/test/resources/features/CucumberTagsExample.feature" }, glue = {"com.cucumber.demo.definitions" }, tags = ("@BlankCredentials and @InValidCredentials"))

The output of the above program is

How to ignore Tags in Cucumber?

To skip a specific test scenario, use not keyword.

@CucumberOptions(features= {"src/test/resources/features/LoginPage.feature"}, glue= {"org.example.definitions"}, tags = ("not @InValidCredentials"))

The output of the above program is

All these syntaxes are valid for Cucumber Version – 6.8.1

The below-mentioned syntax is not valid for Cucumber Version – 6.8.1 and above

AND - {"@BlankCredentials , @InValidCredentials"}
OR - {"@BlankCredentials" , "@InValidCredentials"}
NOT - {"~@InValidCredentials"}

How to run multiple feature files

To run multiple feature files, we can use the below syntax:

@CucumberOptions(features= {"src/test/resources/features/LoginPage.feature","src/test/resources/features/DashboardPage.feature"}, glue= {"org.example.definitions"})

I have mentioned the path of 2 feature files separated by a comma.

We are done! Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!!

Additional Tutorials

Cucumber – What is Feature File in Cucumber
Step Definition in Cucumber
Cucumber – JUnit Test Runner Class
Background in Cucumber
Conditional Hooks in Cucumber
vibssingh

How to write tests in Robot Framework in BDD Format

Last Modified Date

HOME

In this tutorial, we will run the tests in the BDD format in Robot Framework.

What is BDD?

BDD is an Agile software development process in which an application is documented and designed around the behaviour that a user expects to see when interacting with it. BDD helps to avoid bloat, excessive code, unnecessary features, and lack of focus by encouraging developers to focus only on the requested behaviours of an app or program. This methodology combines, augments, and refines test-driven development (TDD) and acceptance testing practices.

The Given-When-Then syntax is a commonly used structure for writing user stories and acceptance criteria in a behaviour-driven development (BDD). It is used to describe the desired behaviour of a system in a clear, concise, and consistent manner.

The structure is broken down into three parts:

  • Given: This section describes the initial state or context of the system. It sets the scene for the scenario being tested.
  • When: This section describes the action or event that occurs. It specifies the trigger for the scenario being tested.
  • Then: This section describes the expected outcome or result of the scenario. It defines the acceptance criteria for the scenario being tested.

Prerequisite:

  1. Install Python
  2. Install PIP
  3. Install Robot Framework
  4. Install Robot framework Selenium Library
  5. Install PyCharm IDE

Please refer to this tutorial to install Robot Framework – How to install and setup Robot Framework for Python.

Implementation Steps:

Step 1.1 – Open PyCharm and create a new project. Go to File and select New Project from the main menu.

Step 1.2 – Choose the project location. Click the “Browse” button next to the Location field and specify the directory for your project.

Deselect the Create a main.py welcome script checkbox because you will create a new Python file for this tutorial.

Click on the “Create” Button.

Step 1.3 – A new dialog appears asking to open the project using any one of the given options. I have selected New Window as I like to have separate windows for each project.

Below is the image of the new project created in PyCharms.

How to run tests in BDD format in Robot Framework?

Step 2 – Create a new directory in the new project

Right-Click on the project, select New->Directory and provide name as Tests

Below is the image of the new directory.

Right-click on the new directory and select New File and provide the name as BDD_Demo.robot as shown below:

Step 3 – Execute the tests

We are now going to write test cases. The test case details will be as follows −

To work with the Robot Framework, we need a locator. A locator is an identifier for the textbox like id, name, class, xpath, css selector, etc.

To know more about locators, refer to these Selenium Tutorials:

 Locators in Selenium – Locate by ID, ClassName,  Name, TagName,  LinkText, PartialLinkText

Dynamic XPath  in Selenium WebDriver

CSS Selector in Selenium WebDriver

Below is an example of tests in BDD format.

*** Settings ***
Documentation       Tests to login to Login Page
Library     SeleniumLibrary

*** Variables ***
${valid_username}     Admin
${valid_password}       admin123
${invalid_password}     45678
${url}      https://opensource-demo.orangehrmlive.com/web/index.php/auth/login
${browser_name}      Chrome
${login_error_message}      css:.oxd-alert-content--error
${dashboard_title}       css:.oxd-topbar-header-breadcrumb-module


*** Test Cases ***

Validate Unsuccessful Login using invalid credentials
    [Tags]    SMOKE
    Given I open the Browser with URL
    When I fill the login form     ${valid_username}       ${invalid_password}
    Then I verify the error message is correct
    And Close Browser Session

Validate successful Login
    [Tags]    UAT
    Given I open the Browser with URL
    When I fill the login form     ${valid_username}       ${valid_password}
    Then I verify Dashboard page opens
    And Close Browser Session

*** Keywords ***

Given I open the Browser with URL
    Create Webdriver    ${browser_name}  executable_path=/Vibha_Personal/RobotFramework_Demo/drivers/${browser_name}
    Go To       ${url}
    Maximize Browser Window
    Set Selenium Implicit Wait    5

When I fill the login form
   [Arguments]    ${username}      ${password}
   Input Text    css:input[name=username]   ${username}
   Input Password    css:input[name=password]   ${password}
   Click Button    css:.orangehrm-login-button

Then I verify the error message is correct
    Element Text Should Be    ${login_error_message}    Invalid credentials

Then I verify Dashboard page opens
    Element Text Should Be    ${dashboard_title}      Dashboard


And Close Browser Session
    Close Browser

All the below-mentioned keywords are derived from SeleniumLibrary except the last one. The functionality of keywords mentioned above:

1. Open Browser  − The keyword opens a new browser instance to the optional URL.

2. Maximize Browser Window – This keyword maximizes the current browser window.

3. Set Selenium Implicit Wait – This keyword sets the implicit wait value used by Selenium.

4. Input Text − This keyword is used to type the given text in the specified textbox identified by the locator name:username.

5. Input Password – This keyword is used to type the given text in the specified password identified by the locator name:password.

The difference compared to Input Text is that this keyword does not log the given password on the INFO level.

6. Click button – This keyword is used to click on the button with location css:.orangehrm-login-button.

7. ${result} – This is a variable that holds the text value of the error message that is located by css:.oxd-alert-content-text

8. Element Text Should Be  – This keyword is used to verify that the element locator contains exact the text expected.

These keywords are present in SeleniumLibrary. To know more about these keywords, please refer to this document – https://robotframework.org/SeleniumLibrary/SeleniumLibrary.htm.

To run this script, go to the command line and go to directory tests.

Step 4 – Execute the tests

We need the below command to run the Robot Framework script.

robot .

The output of the above program is

Step 5 – View Report and Log

We have the test case passed. The Robot Framework generates log.html, output.xml, and report.html by default.

Let us now see the report and log details.

Report

Right-click on report.html. Select Open In->Browser->Chrome(any browser of your wish).

The Report generated by the framework is shown below:

Log

Robot Framework has multiple log levels that control what is shown in the automatically generated log file. The default Robot Framework log level is INFO.

Right-click on log.html. Select Open In->Browser->Chrome(any browser of your wish).

That’s it! Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!!

vibssingh

Robot Framework Tutorials

Last Updated On

HOME

Robot Framework is a generic open-source automation framework. It can be used for test automation and robotic process automation (RPA). RPA is extensively used for Web Application Automation, API Automation, RPA, and Database Testing.

Robot Framework has an easy syntax, utilizing human-readable keywords. Its capabilities can be extended by libraries implemented with Python, Java, or many other programming languages.

Chapter 1 How to Install Python on Windows 11
Chapter 2 How to install PyCharms on Windows 11
Chapter 3 What is Robot Framework
Chapter 4 How to install and setup Robot Framework for Python
Chapter 5 Robot Framework – Working With Browsers Using Selenium Library
Chapter 6 Robot Framework Features – Settings, Libraries, Variables, Keywords, Resources, Reports, Logs
Chapter 7 What are variables in Robot Framework?
Chapter 8 How to handle text box in Robot Framework
Chapter 9 How to handle radio buttons in Robot Framework
Chapter 10 How to handle checkbox in Robot Framework
Chapter 11 How to handle dropdowns in Robot Framework
Chapter 12 How to handle multiple windows in Robot Framework
Chapter 13 How to handle alerts in Robot Framework
Chapter 14 What is Resource File in Robot Framework 
Chapter 15 How to run all the tests from the folder in Robot Framework
Chapter 16 How to implement tagging in Robot Framework
Chapter 17 How to rerun failed tests in Robot Framework
Chapter 18 How to use Drag and Drop in Robot Framework?
Chapter 19 How to set variable values from Runtime command in Robot Framework
Chapter 20 Page Object Model in Robot Framework with Selenium and Python
Chapter 21 Parallel Testing in Robot Framework
Chapter 22 How to run headless tests in Robot Framework 
Chapter 23 Integration of Allure Report with Robot Framework
Chapter 24 How to write tests in Robot Framework in BDD Format

Data-Driven Testing

Chapter 1 Data-Driven Testing in Robot Framework 
Chapter 2 How to load data from CSV files in the Robot Framework?

API Testing

Chapter 1 How to perform API Testing in Robot Framework

CI/CD

Chapter 1 Run Robot Framework Tests in GitLab CI/CD
Chapter 2 How to run Robot Framework in GitHub Actions

Jenkins

Chapter 1 How to integrate Robot Framework with Jenkins
Chapter 2 How to run parameterized Robot Framework tests in Jenkins
vibssingh

Background in Cucumber

Last Updated On

HOME

What is the Background in Cucumber?

The background is used in Cucumber to define a step or series of steps that are shared by all the tests in the feature file.

A Background provides context for the scenarios that follow it. It may include one or more Given steps, which are executed before each scenario but after any Before hooks.

A Background is placed at the same level of indentation as the first Scenario/Example.

Below is an example of a Background in a Feature file.

Feature: Login to HRM Application

  Background:
    Given User is on HRMLogin page "https://opensource-demo.orangehrmlive.com/"

  @ValidCredentials
  Scenario: Login with valid credentials

    When User enters username as "Admin" and password as "admin123"
    Then User should be able to login successfully and new page open

  @MissingUsername
  Scenario: Login with blank username

    When User enters username as " " and password as "admin123"
    Then User should be able to see a message "Required" below Username

In the above example, we have two different scenarios, where a user is successfully able to log in to the application and an unsuccessful attempt to log in. But the common step is to open the website for both scenarios. This is why we created another Scenario for opening the browser but named it Background rather than a Scenario. So that it executes for both Scenarios.

import io.cucumber.java.en.Given;
import io.cucumber.java.en.Then;
import io.cucumber.java.en.When;

public class LoginPageDefinitions {

    @Given("User is on HRMLogin page {string}")
    public void loginTest(String url) {

        System.out.println("I am in Login Page");

    }

    @When("User enters username as {string} and password as {string}")
    public void goToHomePage(String userName, String passWord) {

        System.out.println("Go to Home Page");

    }

    @Then("User should be able to login successfully and new page open")
    public void verifyLogin() {

        System.out.println("Home Page is opened");

    }

    @Then("User should be able to see a message {string} below Username")
    public void verifyMissingUsernameMessage(String message) {

        System.out.println("Login failed with an error message");
    }

}

We need a runner class to execute the feature file. Below is an example of the Runner class.

import io.cucumber.testng.AbstractTestNGCucumberTests;
import io.cucumber.testng.CucumberOptions;

@CucumberOptions(tags = "", features = "src/test/resources/features/LoginPage.feature", glue = "org.example.definitions",
        plugin = {})
public class CucumberRunnerTests extends AbstractTestNGCucumberTests {
}

The output of the above program is

Background with Hooks

Background can contain one or more Given steps, which are run before each scenario, but after any Before hooks.

Below is an example of the background with hooks. The feature file is the same. I’m just adding the hooks to the Step Definition class.

import io.cucumber.java.en.Given;
import io.cucumber.java.en.Then;
import io.cucumber.java.en.When;

public class LoginPageDefinitions {

    @Before()
    public void beforeScenario(){
        System.out.println("Start the browser and Clear the cookies");
    }

    @Given("User is on HRMLogin page {string}")
    public void loginTest(String url) {

        System.out.println("I am in Login Page");

    }

    @When("User enters username as {string} and password as {string}")
    public void goToHomePage(String userName, String passWord) {

        System.out.println("Go to Home Page");

    }

    @Then("User should be able to login successfully and new page open")
    public void verifyLogin() {

        System.out.println("Home Page is opened");

    }

    @Then("User should be able to see a message {string} below Username")
    public void verifyMissingUsernameMessage(String message) {

        System.out.println("Login failed with an error message");
    }

  @After()
    public void afterScenario(){
        System.out.println("Log out the user and close the browser");
    }

}

The output of the above program is

Points to remember

  • The background should not be used to create complicated states unless the client requires that information.
    For example, if the client doesn’t care about the user and site names, use a higher-level step like Given I am logged in as a site owner
  • Keep the Background section brief.
    When reading the scenarios, the client must remember this information. Consider moving some of the irrelevant details into higher-level steps if the Background is longer than four lines.
  • Make your background section stand out
    Use interesting names and try to tell a story. The human brain remembers stories much better than it remembers names like “User A,” “User B,” “Site 1,” and so on.

That’s it! Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!!