Cucumber

vibssingh

How to rerun failed tests twice in Cucumber

HOME

The previous tutorial explained the How to rerun failed tests in Cucumber. There are multiple times that we need to rerun the failed tests twice to overcome the intermittent network or environment issues. This can be achieved by creating multiple TestRunner class.

Table of Contents

  1. Set Up a Runner for First Run of Tests
  2. Set Up a Runner for running the failed tests first time
  3. Set Up a Runner for running the failed tests second time
  4. Mention all the Test Runner details in the testng.xml
  5. Add cucumber-reporting Plugin to pom.xml
  6. Run the tests and Generate the Report

Set Up a Runner for First Run of Tests

In the main test runner, configure Cucumber to generate a JSON report for the initial test run and capture any failed tests in a rerun file. We are using rerun plugin to logs the paths of failed scenarios in a text file – rerun.txt that will be created inside the target folder.

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

@CucumberOptions(features = "src/test/resources/features/LoginPage.feature",
        glue = "com.example.definitions",
        plugin = {
                "pretty",
                "html:target/cucumber-reports/cucumber-report.html",
                "json:target/cucumber-reports/cucumber-report.json",
                "rerun:target/rerun.txt" // Saves paths of failed scenarios
        }
)
public class RunnerTests extends AbstractTestNGCucumberTests {
}

Set Up a Runner for running the failed tests first time

Create a second runner that reads from the rerun.txt file and generates a new rerun1.txt file that contains the path of failed tests and create a separate JSON report for failed test reruns.

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

@CucumberOptions(tags = "",
        features = "@target/rerun.txt",
        glue = "com.example.definitions",
        plugin =  {
                "pretty",
                "html:target/cucumber-reports/cucumber-rerun1-report.html",
                "json:target/cucumber-reports/cucumber-rerun1-report.json",
                "rerun:target/rerun1.txt"
        }
)

public class RunnerTestsFailed extends AbstractTestNGCucumberTests {
}

Set Up a Runner for running the failed tests second time

Create a third runner that reads from the rerun1.txt file and generates a separate JSON report for failed test reruns.

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

@CucumberOptions(tags = "",
        features = "@target/rerun1.txt",
        glue = "com.example.definitions",
        plugin =  {
                "pretty",
                "html:target/cucumber-reports/cucumber-rerun2-report.html",
                "json:target/cucumber-reports/cucumber-rerun2-report.json"
        }
)

public class RunnerTestsSecondFailed extends AbstractTestNGCucumberTests {
}

Mention all the Test Runner details in the testng.xml

We need to mention all the TestRunner class name in the testng.xml. This will run first runner that will generate a file rerun.txt which in turns contain the path of the failed scenarios. Then, second runner will use this new file rerun.txt as input to the feature file and rerun the failed tests and generate second file – rerun1.txt which is used as input to the third Test Runner file. 

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
<suite name="Suite">
    <test  name="Cucumber with TestNG Test">
        <classes>
            <class name="com.example.runner.RunnerTests"/>
            <class name="com.example.runner.RunnerTestsFailed"/>
            <class name="com.example.runner.RunnerTestsSecondFailed"/>
        </classes>
    </test> <!-- Test -->
</suite> <!-- Suite -->

Add cucumber-reporting Plugin to pom.xml

Use the cucumber-reporting plugin by Masterthought to combine the JSON files into a single report. Configure the plugin in your pom.xml to read both the main and rerun JSON files.

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>com.example</groupId>
  <artifactId>POM_Cucumber_TestNG_Demo</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>jar</packaging>

  <name>POM_Cucumber_TestNG_Demo</name>
  <url>http://maven.apache.org</url>

  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <cucumber.version>7.18.1</cucumber.version>
    <selenium.version>4.25.0</selenium.version>
    <testng.version>7.10.2</testng.version>
    <apache.common.version>2.4</apache.common.version>
    <maven.compiler.plugin.version>3.13.0</maven.compiler.plugin.version>
    <maven.surefire.plugin.version>3.3.1</maven.surefire.plugin.version>
    <maven.compiler.source.version>17</maven.compiler.source.version>
    <maven.compiler.target.version>17</maven.compiler.target.version>
    <maven.cucumber.reporting.version>5.8.2</maven.cucumber.reporting.version>
  </properties>

  <dependencies>

    <dependency>
      <groupId>io.cucumber</groupId>
      <artifactId>cucumber-java</artifactId>
      <version>${cucumber.version}</version>
    </dependency>

    <dependency>
      <groupId>io.cucumber</groupId>
      <artifactId>cucumber-testng</artifactId>
      <version>${cucumber.version}</version>
      <scope>test</scope>
    </dependency>

    <!-- Selenium -->
    <dependency>
      <groupId>org.seleniumhq.selenium</groupId>
      <artifactId>selenium-java</artifactId>
      <version>${selenium.version}</version>
    </dependency>

    <!-- TestNG -->
    <dependency>
      <groupId>org.testng</groupId>
      <artifactId>testng</artifactId>
      <version>${testng.version}</version>
      <scope>test</scope>
    </dependency>

    <!-- Cucumber Reporting -->
    <dependency>
      <groupId>net.masterthought</groupId>
      <artifactId>cucumber-reporting</artifactId>
      <version>${maven.cucumber.reporting.version}</version>
    </dependency>

  </dependencies>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>${maven.compiler.plugin.version}</version>
        <configuration>
          <source>${maven.compiler.source.version}</source>
          <target>${maven.compiler.target.version}</target>
        </configuration>
      </plugin>
      
        <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>${maven.surefire.plugin.version}</version>
        <configuration>
          <testFailureIgnore>true</testFailureIgnore>
          <suiteXmlFiles>
            <suiteXmlFile>testng.xml</suiteXmlFile>
          </suiteXmlFiles>
        </configuration>
      </plugin>

      <plugin>
        <groupId>net.masterthought</groupId>
        <artifactId>maven-cucumber-reporting</artifactId>
        <version>${maven.cucumber.reporting.version}</version>

        <executions>
          <execution>
            <id>generate-cucumber-report</id>
            <phase>verify</phase>
            <goals>
              <goal>generate</goal>
            </goals>
            <configuration>
              <projectName>Cucumber Reporting Example</projectName>
              <outputDirectory>target/cucumber-html-reports</outputDirectory>
              <inputDirectory>target</inputDirectory>
              <jsonFiles>
                <!-- Include both main and rerun JSON reports -->
                <param>target/cucumber-reports/cucumber-report.json</param>
                <param>target/cucumber-reports/cucumber-rerun-report.json</param>
                <param>**/*.json</param>
              </jsonFiles>
            </configuration>
          </execution>
        </executions>
      </plugin>

    </plugins>
  </build>
</project>

Run the tests and Generate the Report

Use the below command to run the tests and generate the consolidated Test Report.

mvn clean verify

RunnerTests class generates cucumber-report.json file whereas RunnerTestsFailed generates cucumber-rerun-report.json files are present in target/cucumber-reports folder.

MasterThought plugin uses these json files to generate a consolidated report in target/cucumber-html-reports.

There are different types of HTML reports gets generated as a part of the test execution cycle.

1. feature-overview – This HTML report gives an overall overview of test execution. Main HTML report which covers all different sections like Features, Tags, Steps, and Failures.

2. failures-overview – This HTML report gives an overview of all failed tests.

3. step-overview – This HTML report shows step statistics for the current cycle.

4. tag-overview – This HTML report shows passing and failing statistics for different tags used in test execution.

Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!! Cheers!!

vibssingh

How to create Cucumber Report after rerun of failed tests

Last Updated On

HOME

There are multiple reports produced when the Cucumber failed tests are redone. There is no unified test execution status provided in these reports. To generate a consolidated Cucumber report after rerunning any failed tests, follow these steps:

Table of Contents

  1. Set Up a Runner for First Run of Tests
  2. Set Up a Runner for Failed Tests
  3. Mention both Test Runner details in the testng.xml
  4. Add cucumber-reporting Plugin to pom.xml
  5. Run the tests and Generate the Report

Set Up a Runner for First Run of Tests

In the main test runner, configure Cucumber to generate a JSON report for the initial test run and capture any failed tests in a rerun file. We are using rerun plugin to logs the paths of failed scenarios in a text file – rerun.txt that will be created inside the target folder.

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

@CucumberOptions(features = "src/test/resources/features/LoginPage.feature",
        glue = "com.example.definitions",
        plugin = {
                "pretty",
                "html:target/cucumber-reports/cucumber-report.html",
                "json:target/cucumber-reports/cucumber-report.json",
                "rerun:target/rerun.txt" // Saves paths of failed scenarios
        }
)
public class RunnerTests extends AbstractTestNGCucumberTests {
}

Set Up a Runner for Failed Tests

Create a second runner that reads from the rerun.txt file and generates a separate JSON report for failed test reruns.

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

@CucumberOptions(tags = "",
        features = "@target/rerun.txt",
        glue = "com.example.definitions",
        plugin =  {
                "pretty",
                "html:target/cucumber-reports/cucumber-rerun-report.html",
                "json:target/cucumber-reports/cucumber-rerun-report.json"
        }
)

public class RunnerTestsFailed extends AbstractTestNGCucumberTests {
}

Mention both Test Runner details in the testng.xml

We need to mention both the TestRunner class name in the testng.xml. This will run both the runners sequentially.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
<suite name="Suite">
    <test  name="Cucumber with TestNG Test">
        <classes>
            <class name="com.example.runner.RunnerTests"/>
            <class name="com.example.runner.RunnerTestsFailed"/>
        </classes>
    </test> <!-- Test -->
</suite> <!-- Suite -->

Add cucumber-reporting Plugin to pom.xml

Use the cucumber-reporting plugin by Masterthought to combine the JSON files into a single report. Configure the plugin in your pom.xml to read both the main and rerun JSON files.

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>com.example</groupId>
  <artifactId>POM_Cucumber_TestNG_Demo</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>jar</packaging>

  <name>POM_Cucumber_TestNG_Demo</name>
  <url>http://maven.apache.org</url>

  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <cucumber.version>7.18.1</cucumber.version>
    <selenium.version>4.25.0</selenium.version>
    <testng.version>7.10.2</testng.version>
    <apache.common.version>2.4</apache.common.version>
    <maven.compiler.plugin.version>3.13.0</maven.compiler.plugin.version>
    <maven.surefire.plugin.version>3.3.1</maven.surefire.plugin.version>
    <maven.compiler.source.version>17</maven.compiler.source.version>
    <maven.compiler.target.version>17</maven.compiler.target.version>
    <maven.cucumber.reporting.version>5.8.2</maven.cucumber.reporting.version>
  </properties>

  <dependencies>

    <dependency>
      <groupId>io.cucumber</groupId>
      <artifactId>cucumber-java</artifactId>
      <version>${cucumber.version}</version>
    </dependency>

    <dependency>
      <groupId>io.cucumber</groupId>
      <artifactId>cucumber-testng</artifactId>
      <version>${cucumber.version}</version>
      <scope>test</scope>
    </dependency>

    <!-- Selenium -->
    <dependency>
      <groupId>org.seleniumhq.selenium</groupId>
      <artifactId>selenium-java</artifactId>
      <version>${selenium.version}</version>
    </dependency>

    <!-- TestNG -->
    <dependency>
      <groupId>org.testng</groupId>
      <artifactId>testng</artifactId>
      <version>${testng.version}</version>
      <scope>test</scope>
    </dependency>

    <!-- Cucumber Reporting -->
    <dependency>
      <groupId>net.masterthought</groupId>
      <artifactId>cucumber-reporting</artifactId>
      <version>${maven.cucumber.reporting.version}</version>
    </dependency>

  </dependencies>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>${maven.compiler.plugin.version}</version>
        <configuration>
          <source>${maven.compiler.source.version}</source>
          <target>${maven.compiler.target.version}</target>
        </configuration>
      </plugin>
      
        <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>${maven.surefire.plugin.version}</version>
        <configuration>
          <testFailureIgnore>true</testFailureIgnore>
          <suiteXmlFiles>
            <suiteXmlFile>testng.xml</suiteXmlFile>
          </suiteXmlFiles>
        </configuration>
      </plugin>

      <plugin>
        <groupId>net.masterthought</groupId>
        <artifactId>maven-cucumber-reporting</artifactId>
        <version>${maven.cucumber.reporting.version}</version>

        <executions>
          <execution>
            <id>generate-cucumber-report</id>
            <phase>verify</phase>
            <goals>
              <goal>generate</goal>
            </goals>
            <configuration>
              <projectName>Cucumber Reporting Example</projectName>
              <outputDirectory>target/cucumber-html-reports</outputDirectory>
              <inputDirectory>target</inputDirectory>
              <jsonFiles>
                <!-- Include both main and rerun JSON reports -->
                <param>target/cucumber-reports/cucumber-report.json</param>
                <param>target/cucumber-reports/cucumber-rerun-report.json</param>
                <param>**/*.json</param>
              </jsonFiles>
            </configuration>
          </execution>
        </executions>
      </plugin>

    </plugins>
  </build>
</project>

Run the tests and Generate the Report

Use the below command to run the tests and generate the consolidated Test Report.

mvn clean verify

RunnerTests class generates cucumber-report.json file whereas RunnerTestsFailed generates cucumber-rerun-report.json files are present in target/cucumber-reports folder.

MasterThought plugin uses these json files to generate a consolidated report in target/cucumber-html-reports.

There are different types of HTML reports gets generated as a part of the test execution cycle.

1. feature-overview – This HTML report gives an overall overview of test execution. Main HTML report which covers all different sections like Features, Tags, Steps, and Failures.

2. failures-overview – This HTML report gives an overview of all failed tests.

3. step-overview – This HTML report shows step statistics for the current cycle.

4. tag-overview – This HTML report shows passing and failing statistics for different tags used in test execution.

Congratulations on making it through this tutorial and hope you found it useful! Happy Learning!! Cheers!!

vibssingh

BDD Multiple Choice Answers – MCQ1

HOME

BDD Quiz – You can test your knowledge with this BDD Quiz. 

BDD Multiple Choice Questions – MCQ1

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

vibssingh

What is CucumberOptions in Cucumber?

HOME

In Cucumber, “@CucumberOptions“ is an annotation used to specify various options for running Cucumber tests. It allows you to configure different aspects of how your Cucumber tests are executed. This annotation is typically placed above the test runner class, which is responsible for triggering the execution of Cucumber tests.

1.Command-line arguments have the highest precedence. If you specify options through the CLI, they will override any settings provided by “@CucumberOptions“ or properties files. For example, running the tests with specific options from the terminal.

mvn clean test -Dcucumber.options="--tags @smoke --plugin pretty"

2. The “@CucumberOptions” annotation comes next in the precedence order. Settings configured here will override those provided in properties files but will be overridden by CLI arguments. For example, specifying configurations directly in the test runner class.

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

@RunWith(Cucumber.class)
@CucumberOptions(
         features = "src/test/resources/features",
         glue = "com.mycompany.stepdefinitions",
         plugin = {"pretty", "html:target/cucumber-reports.html", "json:target/cucumber.json"},
         tags = "@smoke",
         monochrome = true,
         dryRun = false
     )

public class RunCucumberTests {
}

3. Configuration settings in properties files have the lowest precedence. These settings will be used if neither CLI arguments nor “@CucumberOptions“ provide a value for a particular option. For example, Creating a “cucumber.properties“ file to specify default configurations.

cucumber.features=src/test/resources/features
cucumber.glue=com.mycompany.stepdefinitions
cucumber.plugin=pretty, html:target/cucumber-reports.html, json:target/cucumber.json
cucumber.tags=@smoke

Configuration Options in CucumberOptions

Below is an example of CucumberOptions

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

@RunWith(Cucumber.class)
@CucumberOptions( features = "src/test/resources/features",
    glue = "com.mycompany.stepdefinitions",
    plugin = {"pretty", "html:target/cucumber-reports.html", "json:target/cucumber.json"},
    tags = "@smoke",
    monochrome = true,
    dryRun = false,
    strict = true,
    name = "Login functionality"  )

public class RunCucumberTest {
}

In this example:

  1. The “features” attribute points to the location of the feature files.
  2. The “glue” attribute points to the package where the step definitions are located.
  3. The “plugin” attribute specifies three plugins: one for pretty output in the console, one for an HTML report, and one for a JSON report.
  4. The “tags” attribute specifies that only scenarios tagged with @smoke will be run.
  5. The “monochrome” attribute is set to true to make the console output more readable.
  6. The “dryRun” attribute is set to false to indicate that the tests should actually be executed.
  7. The “strict” attribute treats undefined and pending steps as errors, ensuring all steps are fully implemented.
  8. The “name” attribute allows running scenarios that match a specific name or pattern using regular expressions.
vibssingh

What is Glue in Cucumber?

Last Updated On

HOME

This tutorial explains the Glue code in Cucumber.

Table of Contents

  1. What is Glue code?
  2. Cucumber Glue Example
  3. How Glue Locate Step Definitions
  4. Multiple StepDefinitions in Glue Code

What is Glue code?

The glue option helps Cucumber locate the step definition file. In the glue cucumber option, we specify the package to load the glue code. Where glue code is our step definitions or hooks.

The glue code in Cucumber performs the following tasks:

– Scans the project for step definitions and associates them with the corresponding steps in the feature files.
– Executes the automation code defined in the step definitions when the corresponding step is encountered during test execution.
– Provides a way to configure Cucumber runtime options, such as defining test hooks, plugins, and other settings.

Cucumber Glue Example

import org.junit.runner.RunWith;
import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
 
@RunWith(Cucumber.class)
@CucumberOptions(plugin = "pretty", features = "src/test/resources/features",
glue = "com.example.customer")
 
public class CucumberRunnerTest {
 
}

This option specifies the package where the step definition classes are located. In this example, the step definitions are expected to be present in the “com.example.customer” package.

How Glue Locate Step Definitions

1. By default, Cucumber expects the step definitions to be in the same package as the Test Runner class.
2. If the “glue“ option is not specified in the Cucumber options, Cucumber will automatically assume that the step definitions are located in the same package as the test runner. Therefore, if your test runner class is “com.example.runner“, Cucumber will consider the “com.example.runner“ package as the default package for locating the step definitions.

You can comment or remove the “glue“ line in the Cucumber options if your test runner and step definitions are in the same package.

Multiple StepDefinitions in Glue Code

If the step definitions are present in 2 different packages, you can separate packages using a comma and double quotes.

glue = {"com.example.customer", "com.example.agents"}

Without proper glue settings, Cucumber will not be able to connect the feature files’ scenarios with the corresponding implementation, resulting in unimplemented step errors.

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

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

Cucumber Multiple-Choice Questions with Answers – MCQ2

Last Updated On

HOME

Are you familiar with Cucumber and want to test your understanding? This post has 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

API Automation with REST Assured, Cucumber and TestNG

Last Updated On

HOME

Cucumber is not an API automation tool, but it works well with other API automation tools.

There are 2 most commonly used Automation Tools for JVM to test API – Rest-Assured and Karate. In this tutorial, I will use RestAssured with Cucumber and TestNG for API Testing.

Table of Contents

  1. What is Rest Assured?
  2. What is Cucumber?
  3. Dependency List
  4. Project Structure
  5. Implementation Steps
    1. Download and Install Java
    2. Download and setup Eclipse IDE on the system
    3. Setup Maven
    4. Create a new Maven Project
    5. Install the Cucumber Eclipse plugin for the Eclipse project (Eclipse Only)
    6. Create source folder src/test/resources
    7. Add dependencies to the project
    8. Add Maven Compiler Plugin and Surefire Plugin
    9. Create a feature file under src/test/resources
    10. Create the Step Definition class or Glue Code
    11. Create a TestNG Cucumber Runner class
    12. Create a testng.xml file
    13. Run the tests from TestNG
    14. Run the tests from the testng.xml
    15. TestNG Report Generation
    16. Run the tests from the Command Line
    17. Cucumber Report Generation

What is Rest Assured?

REST Assured is a Java library that provides a domain-specific language (DSL) for writing powerful, maintainable tests for RESTful APIs. REST Assured can be used easily in combination with existing unit testing frameworks, such as JUnit and TestNG. Rest assured, no matter how complex the JSON structures are, Rest Assured has methods to retrieve data from almost every part of the request and response.

What is Cucumber?

Cucumber is one such open-source tool, which supports Behaviour Driven Development(BDD). In simple words, Cucumber can be defined as a testing framework, driven by plain English. It serves as documentation, automated tests, and development aid – all in one.

Each scenario is a set of steps that the Cucumber must complete. Cucumber validates the software’s compliance with the specification and generates a report indicating success or failure for each scenario.

The cucumber must adhere to some basic syntax rules known as Gherkin to comprehend the scenarios.

In this tutorial, I will explain creating a framework for the testing of Rest API in Cucumber BDD.

Dependency List

  1. Cucumber – 7.18.0
  2. Java 17
  3. TestNG – 7.10.2
  4. Maven – 3.9.6
  5. Rest Assured – 5.4.0
  6. Maven Compiler – 3.13.0
  7. Maven Surefire – 3.2.5

Project Structure

Implementation Steps

Step 1 – Download and Install Java

Cucumber and Rest-Assured need Java to be installed on the system to run the tests. Click here to learn How to install Java.

Step 2 – Download and setup Eclipse IDE on the system

The Eclipse IDE (integrated development environment) provides strong support for Java developers. Click here to learn How to install Eclipse.

Step 3 – Setup Maven

To build a test framework, we need to add several dependencies to the project. Click here to learn How to install Maven.

Step 4 – Create a new Maven Project

File -> New Project-> Maven-> Maven project-> Next -> Enter Group ID & Artifact ID -> Finish

Click here to learn How to create a Maven project

Step 5 – Install the Cucumber Eclipse plugin for the Eclipse project (Eclipse Only)

The Cucumber plugin is an Eclipse plugin that allows Eclipse to understand the Gherkin syntax. Cucumber Eclipse Plugin highlights the keywords present in the Feature File. To install Cucumber Eclipse Plugin, please refer to this tutorial – How to install Cucumber Eclipse Plugin.

Step 6 – Create source folder src/test/resources

Create source folder src/test/resources to create test scenarios in the Feature file.

A new Maven Project is created with 2 folders – src/main/java and src/test/java. To create test scenarios, we need a new source folder called – src/test/resources. To create this folder, right-click on your Maven project ->select New ->Java, and then Source Folder.

Mention the source folder name as src/test/resources and click the Next button. This will create a source folder under your new Maven project.

Step 7 – Add dependencies to the project

Add Rest Assured, Cucumber, and TestNG dependencies in the pom.xml/build.gradle.
REST Assured includes JsonPath and XmlPath as transitive dependencies.

<properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <rest.assured.version>5.4.0</rest.assured.version>
    <cucumber.version>7.18.0</cucumber.version>
    <testng.version>7.10.2</testng.version>
    <maven.compiler.plugin.version>3.13.0</maven.compiler.plugin.version>
    <maven.compiler.source>17</maven.compiler.source>
    <maven.compiler.target>17</maven.compiler.target>
    <maven.surefire.plugin.version>3.2.5</maven.surefire.plugin.version>
  </properties>

  <dependencies>

    <!-- Rest Assured -->
    <dependency>
      <groupId>io.rest-assured</groupId>
      <artifactId>rest-assured</artifactId>
      <version>${rest.assured.version}</version>
      <scope>test</scope>
    </dependency>

    <!-- Cucumber with TestNG -->
    <dependency>
      <groupId>io.cucumber</groupId>
      <artifactId>cucumber-testng</artifactId>
      <version>${cucumber.version}</version>
    </dependency>

    <!-- Cucumber with Java -->
    <dependency>
      <groupId>io.cucumber</groupId>
      <artifactId>cucumber-java</artifactId>
      <version>${cucumber.version}</version>
    </dependency>

    <!-- TestNG -->
    <dependency>
      <groupId>org.testng</groupId>
      <artifactId>testng</artifactId>
      <version>${testng.version}</version>
      <scope>test</scope>
    </dependency>

  </dependencies>

Step 8 – Add Maven Compiler Plugin and Surefire Plugin

The compiler plugin is used to compile the source code of a Maven project. This plugin has two goals, which are already bound to specific phases of the default lifecycle:

  • compile – compile main source files
  • testCompile – compile test source files
 <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>${maven.compiler.plugin.version}</version>
        <configuration>
          <source>${maven.compiler.source}</source>
          <target>${maven.compiler.target}</target>
        </configuration>
      </plugin>

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>${maven.surefire.plugin.version}</version>
        <configuration>
          <suiteXmlFiles>
            <suiteXmlFile>testng.xml</suiteXmlFile>
          </suiteXmlFiles>
        </configuration>
      </plugin>
    </plugins>
  </build>

The complete POM.xml will look like something below:

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
  <modelVersion>4.0.0</modelVersion>

  <groupId>com.example</groupId>
  <artifactId>RestAPI_Cucumber_TestNG_Demo</artifactId>
  <version>1.0-SNAPSHOT</version>
  <packaging>jar</packaging>

  <name>RestAPI_Cucumber_TestNG_Demo</name>
  <url>http://maven.apache.org</url>

  <properties>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <rest.assured.version>5.4.0</rest.assured.version>
    <cucumber.version>7.18.0</cucumber.version>
    <testng.version>7.10.2</testng.version>
    <maven.compiler.plugin.version>3.13.0</maven.compiler.plugin.version>
    <maven.compiler.source>17</maven.compiler.source>
    <maven.compiler.target>17</maven.compiler.target>
    <maven.surefire.plugin.version>3.2.5</maven.surefire.plugin.version>
  </properties>

  <dependencies>

    <!-- Rest Assured -->
    <dependency>
      <groupId>io.rest-assured</groupId>
      <artifactId>rest-assured</artifactId>
      <version>${rest.assured.version}</version>
      <scope>test</scope>
    </dependency>

    <!-- Cucumber with TestNG -->
    <dependency>
      <groupId>io.cucumber</groupId>
      <artifactId>cucumber-testng</artifactId>
      <version>${cucumber.version}</version>
    </dependency>

    <!-- Cucumber with Java -->
    <dependency>
      <groupId>io.cucumber</groupId>
      <artifactId>cucumber-java</artifactId>
      <version>${cucumber.version}</version>
    </dependency>

    <!-- TestNG -->
    <dependency>
      <groupId>org.testng</groupId>
      <artifactId>testng</artifactId>
      <version>${testng.version}</version>
      <scope>test</scope>
    </dependency>

  </dependencies>

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-compiler-plugin</artifactId>
        <version>${maven.compiler.plugin.version}</version>
        <configuration>
          <source>${maven.compiler.source}</source>
          <target>${maven.compiler.target}</target>
        </configuration>
      </plugin>

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-surefire-plugin</artifactId>
        <version>${maven.surefire.plugin.version}</version>
        <configuration>
          <suiteXmlFiles>
            <suiteXmlFile>testng.xml</suiteXmlFile>
          </suiteXmlFiles>
        </configuration>
      </plugin>
    </plugins>
  </build>
</project>

Step 9 – Create a feature file under src/test/resources

Create a folder with name features. Now, create the feature file in this folder. The feature file should be saved with the extension .feature. This feature file contains the test scenarios created to test the application. The Test Scenarios are written in Gherkins language in the format of Given, When, Then, And, But.

Below is an example of a Test Scenario where we are using the GET method to get the information from the API.

Feature: Validation of get method

  @GetUserDetails
  Scenario Outline: Send a valid Request to get user details

    Given I send a request to the URL to get user details
    Then the response will return status <statusCode> and id <id> and email "<employee_email>" and first name "<employee_firstname>" and last name "<employee_lastname>"

    Examples:
    | statusCode | id  | employee_email          | employee_firstname | employee_lastname |
    | 200        | 2   | janet.weaver@reqres.in  | Janet              | Weaver            |

Step 10 – Create the Step Definition class or Glue Code

StepDefinition acts as an intermediate to your runner and feature file. It stores the mapping between each step of the scenario in the Feature file. So when you run the scenario, it will scan the step definition file to check the matched glue or test code.

import io.cucumber.java.en.Given;
import io.cucumber.java.en.Then;
import io.restassured.http.ContentType;
import io.restassured.response.ValidatableResponse;

import static io.restassured.RestAssured.given;
import static org.hamcrest.Matchers.equalTo;

public class APIDemoDefinitions {

    private ValidatableResponse validatableResponse;
    private String endpoint = "https://reqres.in/api/users/2";

    @Given("I send a request to the URL to get user details")
    public void sendRequest(){
        validatableResponse = given().contentType(ContentType.JSON)
                .when().get(endpoint).then();

        System.out.println("Response :"+validatableResponse.extract().asPrettyString());
    }

    @Then("the response will return status {int} and id {int} and email {string} and first name {string} and last name {string}")
    public void verifyStatus(int expectedStatusCode, int expectedId, String expectedEmail, String expectedFirstName, String expectedLastName){

        validatableResponse.assertThat().statusCode(expectedStatusCode).body("data.id",equalTo(expectedId)).and()
                .body("data.email",equalTo(expectedEmail)).body("data.first_name",equalTo(expectedFirstName))
                .body("data.last_name",equalTo(expectedLastName));

    }
}

To use REST assured effectively it’s recommended to statically import methods from the following classes:

io.restassured.RestAssured.*
io.restassured.matcher.RestAssuredMatchers.*
org.hamcrest.Matchers.*

Step 11 – Create a TestNG Cucumber Runner class

A runner will help us run the feature file and act as an interlink between the feature file and the StepDefinition Class.

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

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

}

Note:- The name of the Runner class should end with Test otherwise we can’t run the tests using Command-Line.

Step 12 – Create a testng.xml file

Create a testng.xml at the root of the project.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
<suite name="Suite">
    <test  name="Rest Assured, Cucumber with TestNG Test">
        <classes>
            <class name="com.example.runner.CucumberRunnerTests"/>
        </classes>
    </test> <!-- Test -->
</suite> <!-- Suite -->

Step 13 – Run the tests from TestNG

You can execute the test script by right-clicking on TestRunner class -> Run As TestNG (Eclipse).

You can execute the test script by right-clicking on TestRunner class -> Run CucumberRunnerTests (IntelliJ).

Step 14 – Run the tests from the testng.xml

Right-click on the testng.xml. Click on Run’...\testng.xml’.

Step 15 – TestNG Report Generation

TestNG generates various types of reports under the test-output or target folder like emailable-report.html, index.html, and testng-results.xml.

We are interested in the ‘emailable-report.html’ report. Open “emailable-report.html“, as this is an HTML report, and open it with the browser. The below image shows emailable-report.html.

emailable-report.html

Index.html

TestNG also produces “index.html” report, and it resides under the test-output folder. The below image shows the index.html report.

Step 16 – Run the tests from the Command Line

Run the below command in the command prompt to run the tests and to get the test execution report.

mvn clean test

The output of the above program is

Step 17 – Cucumber Report Generation

To get Cucumber Test Reports, add cucumber.properties under src/test/resources and add the below instruction in the file.

cucumber.publish.enabled=true

The complete code can be found here – vibssingh/RestAPI_Cucumber_TestNG_Demo.

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

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.

Sample Feature File

@LoginPage
Feature: Login to HRM Application
  
   @ValidCredentials
   Scenario: Login with valid credentials
     
   Given User is on HRMLogin page "https://opensource-demo.orangehrmlive.com/"
    When User enters username as "Admin" and password as "admin123"
    Then User should be able to login successfully and new page open

To know more about the Feature File, please refer to this – Cucumber Tutorial – What is Feature File in Cucumber

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.

Sample Test Runner Class

import org.junit.runner.RunWith;
import io.cucumber.junit.Cucumber;
import io.cucumber.junit.CucumberOptions;
 
@RunWith(Cucumber.class)
@CucumberOptions(plugin = "pretty", features = "src/test/resources/Features/MyHoliday.feature", tags = "@BookOneWayFlight")
 
public class CucumberRunnerTest {
 
}

To know more about the Test Runner, please refer to this – Cucumber – JUnit Test Runner Class.

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.

To know more about the Step Definition, please refer to this – Step Definition in Cucumber.

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

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

To know more about the Background, please refer to this – Background in Cucumber.

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

To know more about the Scenario Outline, please refer to this – Data Driven Testing using Scenario Outline in Cucumber.

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

To know more about the Hooks, please refer to this – Hooks in Cucumber.

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

To know more about the Tags, please refer to this – Tags in Cucumber.

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