Back to Interview Prep

</>

Technology

Cucumber

Difficulty

Intermediate

Experience

Intermediate

Type

Interview Q&A

AutomateQA Team

QA Automation Engineers

June 15, 2026

Interview Question

How do you handle step definition ambiguity in Cucumber?

Answer

Step Definition Ambiguity in Cucumber

What Is Ambiguity?

An AmbiguousStepDefinitionException is thrown when Cucumber finds two or more step definition methods whose expression/regex matches the same Gherkin step text.

CODE

io.cucumber.ambiguity.AmbiguousStepDefinitionsException:
"When the user clicks the button" matches more than one step definition:
  - "the user clicks the button" in LoginSteps.java:25
  - "the user clicks the {word} button" in CommonSteps.java:40

Root Cause Example

Java

// LoginSteps.java
@When("the user clicks the button")
public void clickButton() { ... }

// CommonSteps.java
@When("the user clicks the {word} button")
public void clickNamedButton(String buttonName) { ... }

When feature file has: When the user clicks the button → BOTH match → ambiguity error.

Fix 1: Make Expressions More Specific

Java

// Be explicit — add context to the step text
@When("the user clicks the login submit button")
public void clickLoginButton() { ... }

@When("the user clicks the {word} action button")
public void clickActionButton(String buttonName) { ... }

Fix 2: Use Anchors in Regex

Java

// BAD — too broad
@When("clicks the button")
// matches "When the user clicks the button" and "When admin clicks the button"

// GOOD — anchored
@When("^the user clicks the submit button$")
public void clickSubmitButton() { ... }

Fix 3: Consolidate into One Flexible Method

Java

// Replace both conflicting steps with one
@When("the user clicks the {string} button")
public void clickButton(String buttonLabel) {
    if (buttonLabel.equalsIgnoreCase("login")) {
        loginPage.clickLoginButton();
    } else if (buttonLabel.equalsIgnoreCase("register")) {
        registerPage.clickRegisterButton();
    }
}

Fix 4: Rename Conflicting Step Text

Update both the feature file AND step definition to use unique language:

Gherkin

-- Before (ambiguous)
When the user clicks the button

-- After (unambiguous)
When the user submits the login form

Java

@When("the user submits the login form")
public void submitLoginForm() { ... }

How to Detect Ambiguity Early

Java

// Run with dryRun=true
@CucumberOptions(dryRun = true)

dryRun will catch ambiguous steps before any actual test runs.

Best Practice: Consistent Naming Convention

CODE

Given the <actor> is on the <page> page
When the <actor> clicks the <label> button
When the <actor> enters <value> in the <field> field
Then the <element> should <matcher> <expected>

Consistent patterns prevent ambiguity from arising in the first place.