Conditional Hooks in Cucumber


In the previous tutorial, I explained Hooks in Cucumber. In this tutorial, I will explain Condition Hooks in Cucumber.

Hooks can be conditionally selected for execution based on the tags of the scenario. These are called Condition or Tagged Hooks.

Tagged Hooks are much like the scenario hooks, but the only difference is that they are executed before and after the specified tag.

These Tagged hooks will be very specific to the particular tags, so these are not common for all scenarios.

So basically, they can also be run in the following two ways:

  • Before (‘tagName’)
  • After (‘tagName’)

Why do we need Tagged Hooks?

Suppose there are 3 different sets of scenarios. The prerequisites of these scenarios are different, like they have to open different browsers. So, we don’t want to have a common hook for all the scenarios. In this case, we can create a tagged hook to satisfy the requirement of each scenario.

In the below example, there are 3 tags – ChromeBrowser, FireFoxBrowser, and EdgeBrowser. I want to run the hook which has the specified tag for that scenario. For Example, I want @After and @Before hooks related to Chrome Browser should be executed for tag – @ChromeBrowser.

Below is the feature file which has 3 different scenarios.

Feature: Conditional or Tagged Hooks
Scenario: Open Chrome Browser
Given I want to open Google Chrome Browser

Scenario: Open Firefox Browser
Given I want to open Mozilla Firefox Browser

Scenario: Open Edge Browser
Given I want to open Microsoft Edge Browser

Below is the Step Definition for the above feature file.

package com.Cucumber;


public class ConditionalHooksExampleDefinitions {
	@Given("I want to open Google Chrome Browser")
	public void chrome() throws Throwable {
	    System.out.println("I want to open Google Chrome Browser");

	@Given("I want to open Mozilla Firefox Browser")
	public void firefox() throws Throwable {
		System.out.println("I want to open Mozilla Firefox Browser");

	@Given("I want to open Microsoft Edge Browser")
	public void edge() throws Throwable {
		System.out.println("I want to open Microsoft Edge Browser");


Hooks can be defined in the same class or different. I have defined Hooks in a separate class.

package com.Cucumber;


public class Hooks {
    public void beforeStep(){
        System.out.println("@@@@@@@@@@@@@@@ Before Step @@@@@@@@@@@@@@@@@");
    public void afterStep(){
        System.out.println("@@@@@@@@@@@@@@@@  After Step @@@@@@@@@@@@@@@@");
    public void beforeGoogle(){
        System.out.println("******* before Chrome *******");
    public void beforeFirefox(){
        System.out.println("$$$$$$$$$$ before FireFox $$$$$$$$$$");

    public void beforeEdge(){
		System.out.println("============ before Edge =============");
    public void afterGoogle(){
        System.out.println("********* After Google *********");

    public void afterFireFox(){
		System.out.println("$$$$$$$$$$$ After FireFox $$$$$$$$$$");

    public void afterEdge(){
        System.out.println("============ After Edge ==============");


There is no change in the Test Runner Class.

package com.Cucumber;

import org.junit.runner.RunWith;

import cucumber.api.CucumberOptions;
import cucumber.api.junit.Cucumber;

@CucumberOptions(monochrome = true, plugin = "pretty", features = "src/test/resources/features/ConditionalHooksExample.feature", tags = {
		"" })
public class MyRunner {


The execution Result looks like something below

  1. At the start of execution, @Before(“@ChromeBrowser”) {Scenario Hook} is executed.
  2. After that @BeforeStep (Step Hook) hook is executed.
  3. The given statement of the @ChromeBrowser tag is executed in the third step.
  4. The fourth step is to execute @AfterStep.
  5. Now, at the last, the @After(“@ChromeBrowser”) hook is executed. Similarly, the same sequence is followed for FireFox and Edge Scenarios.

Cucumber Tutorials


BDD is a set of practices that helps to reduce the rework caused by misunderstanding or vague requirements, narrow the communication gaps between development team, testing team and customers and promote continuous communication among them. Cucumber is one such open source tool, which supports Behavior 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 a development aid – all in one.

Chapter 1   Introduction of Cucumber Testing Tool (BDD Tool)
Chapter 2 How to install Cucumber Eclipse Plugin
Chapter 3 How to setup Cucumber with Eclipse
Chapter 4 Cucumber – What is Gherkin
Chapter 5 Cucumber – What is Feature File in Cucumber
Chapter 6 Step Definition in Cucumber
Chapter 7 Cucumber – JUnit Test Runner Class
Chapter 8 Cucumber Tutorial – Cucumber Reports
Chapter 9 Cucumber Report Service
Chapter 10 Data Driven Testing using Scenario Outline in Cucumber
Chapter 11 DataTables in Cucumber
Chapter 12 Hooks in Cucumber
Chapter 13 Tags in Cucumber
Chapter 14 Conditional Hooks in Cucumber
Chapter 15 Run Cucumber Test from Command Line
Chapter 16 Integration of Cucumber with Selenium and JUnit
Chapter 17 Page Object Model with Selenium, Cucumber and JUnit
Chapter 18 Parallel Testing in Cucumber with JUnit
Chapter 19 Parallel Testing in Cucumber with TestNG
Chapter 20 Rest API Test in Cucumber BDD
Chapter 21 Integration of Cucumber with Selenium and TestNG
Chapter 22 Dependency Injection in Cucumber using Pico-Container
Chapter 23 Integration of Cucumber with Selenium and TestNG
Chapter 24 Integration Testing of Springboot with Cucumber and JUnit4


Chapter 1 How To Create Gradle Project with Cucumber to test Rest API
Chapter 2 Run Gradle Cucumber Tests from Command Line