Test your Cucumber knowledge with a free interactive quiz — 20 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What is a commonly cited risk or criticism of BDD/Cucumber-style testing if not used carefully?
Questions in this quiz
What is a commonly cited risk or criticism of BDD/Cucumber-style testing if not used carefully?
What is a "step definition" in Cucumber?
What is Gherkin, and what is its relationship to Cucumber?
What is the purpose of "Background" in a Gherkin feature file?
What is the purpose of a "Feature" description block (the plain-text summary that can follow the `Feature:` keyword, before any scenarios) in a Gherkin file?
What is the general relationship between Cucumber and a browser automation tool like Selenium or Playwright, when Cucumber is used for UI/end-to-end testing?
Why might a team choose to write acceptance/integration-level tests in Cucumber/Gherkin format specifically, rather than writing them directly as plain code in a framework like Jest or JUnit?
What is a "Data Table" in Gherkin, and how does it differ from a Scenario Outline's `Examples` table?
What does the `And` (or `But`) keyword do in a Gherkin scenario?
What is Cucumber?
What is a reasonable criterion for deciding whether a given test scenario is worth writing in Cucumber/Gherkin format versus writing it as a plain code-based test?
What is a "Scenario Outline" in Gherkin, and what problem does it solve?