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 the value of Cucumber's "living documentation" characteristic, where feature files serve simultaneously as both executable tests and readable specifications?
Questions in this quiz
What is the value of Cucumber's "living documentation" characteristic, where feature files serve simultaneously as both executable tests and readable specifications?
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 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 a "Feature file" in Cucumber?
What is Cucumber?
How does a step definition typically match a specific Gherkin step's text, especially when the step includes dynamic values (like a specific number or name)?
What is Gherkin, and what is its relationship to Cucumber?
What is a "Scenario Outline" in Gherkin, and what problem does it solve?
What is a "Tag" in Cucumber (like `@smoke` or `@wip` written above a Scenario or Feature)?
What is a "Hook" in Cucumber (like `Before` and `After`)?
What is a "Data Table" in Gherkin, and how does it differ from a Scenario Outline's `Examples` table?
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?