Cucumber Interview Questions (2026)
Cucumber interview questions test BDD skill across Gherkin, features, scenarios, step definitions, hooks, tags, data tables, scenario outlines, reports, and maintainability.
45 questions with answersWhat Is Cucumber?
Key Takeaways
- ✓Cucumber is a BDD tool that runs executable specifications written in Gherkin.
- ✓Interviewers ask about features, scenarios, Given When Then, step definitions, hooks, tags, data tables, and scenario outlines.
- ✓Strong answers explain behavior in business language and keep step definitions reusable without becoming vague.
- ✓Cucumber works best when product, QA, and engineering agree on examples before or during development.
Cucumber is a tool for behavior driven development. It runs scenarios written in Gherkin, a plain text format that describes behavior with Given, When, and Then steps. In interviews, Cucumber questions check whether you can write clear examples, them connects to step definitions, manage hooks and tags, and avoid turning feature files into noisy automation scripts.
Watch: Cucumber BDD Framework Full Course
Video: Cucumber BDD Framework Full Course (Naveen AutomationLabs, YouTube)
Test yourself and earn a certificate
6 quick questions. Score 70%+ to download your Cucumber certificate.
All Questions on This Page
45 questions- 1. What is Cucumber?
- 2. What is BDD?
- 3. What is Gherkin?
- 4. What is a feature file?
- 5. What is a scenario?
- 6. What does Given mean?
- 7. What does When mean?
- 8. What does Then mean?
- 9. What is a step definition?
- 10. What is Background in Cucumber?
- 11. What is a Scenario Outline?
- 12. What are Examples in Cucumber?
- 13. What is a Data Table?
- 14. What are tags in Cucumber?
- 15. What are hooks in Cucumber?
- 16. Write a Cucumber scenario for login.
- 17. When would you use Scenario Outline?
- 18. When would you use a Data Table?
- 19. How do you write a good step definition?
- 20. How do you avoid duplicate step definitions?
- 21. How do you use tags in CI?
- 22. How do you capture screenshots on scenario failure?
- 23. When should Background be used?
- 24. How does Cucumber work with Selenium?
- 25. Can Cucumber test APIs?
- 26. How do you organize feature files?
- 27. How do you manage test data in Cucumber?
- 28. What do you check in a feature file review?
- 29. What should Cucumber reports show?
- 30. When should you not use Cucumber?
- 31. Feature files say 'click login button' and 'type email'. What is wrong?
- 32. A feature has 80 scenarios. What do you do?
- 33. One step matches multiple definitions. What causes this?
- 34. A Background hides ten setup steps. What is the risk?
- 35. A project has many inconsistent tags. What changes?
- 36. A UI redesign breaks many Cucumber steps. What do you improve?
- 37. Product owners never read feature files. What does that mean?
- 38. A Scenario Outline has 100 rows. What is the risk?
- 39. A Cucumber scenario fails randomly. What do you inspect?
- 40. A UI scenario does long setup through the browser. What improves it?
- 41. A Then step says 'the test passes'. What is wrong?
- 42. The step library has hundreds of near-duplicate steps. What do you do?
- 43. Can acceptance criteria become Cucumber scenarios?
- 44. Cucumber reports show step failures but no evidence. What do you add?
- 45. What makes a Cucumber answer senior?
Cucumber Fundamentals
Foundational15 questionsStart here. These are the definitions and first-principle checks that open most rounds.
Q1. What is Cucumber?
Cucumber is a BDD tool that runs behavior scenarios written in Gherkin.
It connects plain text examples to step definition code.
Cucumber changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Watch a deeper explanation
Video: Cucumber BDD Framework Full Course (Naveen AutomationLabs, YouTube)
Q2. What is BDD?
BDD is a practice where teams define expected behavior through concrete examples.
Cucumber is a tool that can automate those examples.
BDD changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q3. What is Gherkin?
Gherkin is the language used to write Cucumber feature files.
It uses keywords such as Feature, Scenario, Given, When, and Then.
Gherkin changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q4. What is a feature file?
A feature file contains one feature and its behavior scenarios in Gherkin.
It should describe business behavior, not automation details.
feature file changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
| Answer part | What to say | Evidence to mention |
|---|---|---|
| Definition | feature file in one direct sentence. | Official docs or course material |
| Use case | The work where it changes a decision. | Dataset, model, query, dashboard, or pipeline |
| Risk | What breaks when it is misunderstood. | Metric, log, test result, or review note |
Q5. What is a scenario?
A scenario is a concrete example of behavior with preconditions, action, and expected result.
Keep scenarios focused and readable.
scenario changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Watch a deeper explanation
Video: BDD and Cucumber Tutorial (Automation Step by Step, YouTube)
Q6. What does Given mean?
Given describes the starting context or precondition.
It should set the state, not perform the main action.
Given changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q7. What does When mean?
When describes the action or event being tested.
Usually one main user action belongs here.
When changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q8. What does Then mean?
Then describes the expected outcome.
It should be observable and testable.
Then changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q9. What is a step definition?
A step definition is code that maps a Gherkin step to automation logic.
It should be reusable but not so generic that meaning is lost.
step definition changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
@Then("the order confirmation is shown")
public void orderConfirmationIsShown() {
Assert.assertTrue(orderPage.confirmationVisible());
}Q10. What is Background in Cucumber?
Background defines common Given steps that run before each scenario in a feature.
Use it for simple shared context, not long hidden setup.
Background changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q11. What is a Scenario Outline?
A Scenario Outline runs the same scenario with multiple rows of examples.
It is useful for data variations.
Scenario Outline changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q12. What are Examples in Cucumber?
Examples provide data rows for a Scenario Outline.
Keep rows meaningful and not too large.
Examples changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q13. What is a Data Table?
A Data Table passes structured data from a step into step definition code.
It works well for forms, permissions, and lists.
Data Table changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Watch a deeper explanation
Video: Cucumber Framework Tutorial (The Testing Academy, YouTube)
Q15. What are hooks in Cucumber?
Hooks run setup or cleanup code before or after scenarios.
Use hooks for environment setup, screenshots, and cleanup, not hidden behavior.
hooks changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Cucumber run flow
Cucumber Practical Interview Questions
Intermediate15 questionsThese questions test whether you can apply the topic to real data, real code, and messy constraints.
Q16. Write a Cucumber scenario for login.
Describe user state, login action, and visible outcome in business terms.
Avoid mentioning locators in the feature file.
write login scenario changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Scenario: Active user signs in
Given the user has an active account
When the user signs in with valid credentials
Then the dashboard is shownQ17. When would you use Scenario Outline?
Use it when the same behavior should be checked with several meaningful input rows.
Do not turn it into a giant spreadsheet.
use Scenario Outline changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q18. When would you use a Data Table?
Use it when a step needs structured data, such as form fields, permission rows, or cart items.
Data tables should stay readable.
use Data Table changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q19. How do you write a good step definition?
Map the business phrase to clear code that performs setup, action, or assertion.
Keep UI details inside page or helper code.
write step definition changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q20. How do you avoid duplicate step definitions?
Use consistent wording, review existing steps, and name behavior instead of click details.
Duplicate steps make maintenance painful.
avoid duplicate steps changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q22. How do you capture screenshots on scenario failure?
Use an After hook that checks scenario status and attaches screenshot evidence.
Failure evidence should map to scenario name.
capture screenshot changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q23. When should Background be used?
Use it for short common context that every scenario in the feature needs.
If readers forget hidden setup, it is too long.
use Background changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q24. How does Cucumber work with Selenium?
Cucumber runs scenario steps, and step definitions call Selenium or page objects to operate the browser.
Cucumber describes behavior. Selenium performs browser actions.
connect Selenium changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q25. Can Cucumber test APIs?
Yes, step definitions can call API clients and assert responses.
Use Cucumber only if the scenarios are business-readable.
write API Cucumber changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Watch a deeper explanation
Video: Cucumber Data Tables (Naveen AutomationLabs, YouTube)
Q26. How do you organize feature files?
Group by business capability, keep scenarios focused, and avoid mixing unrelated flows in one file.
Feature files are communication assets.
organize features changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q27. How do you manage test data in Cucumber?
Use named personas, setup APIs, fixtures, or scenario data while keeping the feature file readable.
Avoid hardcoding secrets or brittle IDs.
handle test data changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q28. What do you check in a feature file review?
Check behavior clarity, business wording, concrete examples, duplication, hidden setup, and assertion value.
Feature file review includes non-testers when possible.
review feature file changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q29. What should Cucumber reports show?
Show feature, scenario, step status, error, screenshot or attachment, duration, tags, and build metadata.
Reports should support triage.
run reports changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q30. When should you not use Cucumber?
Avoid it for low-level unit tests, simple technical checks, and suites where no one reads the feature files.
Cucumber adds value when examples improve shared understanding.
decide Cucumber fit changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Cucumber Advanced Scenarios
Advanced15 questionsAdvanced rounds test trade-offs, failure modes, and whether the decision can hold up under production pressure.
Q31. Feature files say 'click login button' and 'type email'. What is wrong?
They describe automation mechanics instead of behavior.
Use business phrasing and keep clicks in step code.
click-heavy steps changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q32. A feature has 80 scenarios. What do you do?
Group behavior, remove duplicates, move low-level checks to lower layers, and keep representative examples.
Cucumber is not a dumping ground for every check.
too many scenarios changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q33. One step matches multiple definitions. What causes this?
Step patterns are too broad or duplicated.
Tighten wording and remove duplicates.
ambiguous step changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q35. A project has many inconsistent tags. What changes?
Define allowed tags, ownership, and CI mapping.
Tags are part of execution design.
tag chaos changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q36. A UI redesign breaks many Cucumber steps. What do you improve?
Keep locators in page objects or helpers and keep step wording behavior-based.
Business steps should survive UI details where possible.
brittle page steps changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q37. Product owners never read feature files. What does that mean?
Cucumber may not be delivering BDD value.
It may still run tests, but the collaboration benefit is gone.
product ignores features changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q38. A Scenario Outline has 100 rows. What is the risk?
It becomes hard to read and slow to diagnose.
Use representative examples or move broad data checks lower.
scenario outline abuse changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q39. A Cucumber scenario fails randomly. What do you inspect?
Check step code, waits, data, browser state, hooks, environment, and hidden dependencies.
Cucumber itself is rarely the root cause.
flaky Cucumber test changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q41. A Then step says 'the test passes'. What is wrong?
It has no observable product outcome.
Then should state what the user or system sees.
Then step weak changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q42. The step library has hundreds of near-duplicate steps. What do you do?
Consolidate wording, remove unused steps, and set naming guidelines.
A messy step library slows every new scenario.
step library bloat changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q43. Can acceptance criteria become Cucumber scenarios?
Yes, when they are concrete examples with clear Given, When, Then behavior.
Not every acceptance note needs automation.
manual acceptance criteria changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q44. Cucumber reports show step failures but no evidence. What do you add?
Attach screenshots, logs, request IDs, and build metadata from hooks.
Reports should shorten triage.
report unreadable changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Q45. What makes a Cucumber answer senior?
It connects BDD collaboration, readable examples, maintainable steps, tag strategy, evidence, and right-layer testing.
Senior candidates know when Cucumber helps and when it adds noise.
senior Cucumber answer changes Cucumber decisions by affecting the chosen method, the failure mode, or the validation step. Reliable evidence comes from a metric, test result, query output, log, or review note.
Cucumber vs TestNG vs Selenium
Cucumber is not a replacement for Selenium or TestNG. It sits at the behavior specification layer and often calls automation code underneath.
| Tool | Main job | Interview focus | Common misuse |
|---|---|---|---|
| Cucumber | Readable behavior scenarios | Gherkin, steps, hooks, tags, examples | Using it for every low-level test |
| Selenium | Browser automation | Locators, waits, actions, assertions | Writing business rules inside page clicks |
| TestNG or JUnit | Test running and lifecycle | Annotations, assertions, reports, groups | Making business examples unreadable |
| Manual examples | Explore and clarify behavior | Acceptance criteria and edge cases | Skipping automation where repeat value is high |
Cucumber interview topic weight
Good Cucumber interviews care about readable examples and maintainable steps.
Scale: Hyring editorial score for interview preparation, not an external benchmark.
- Gherkin: behavior examples
- Steps: implementation mapping
- Hooks: setup and cleanup
- Tool syntax: supporting detail
How to Prepare for a Cucumber Interview
Prepare by writing three feature files: login, checkout, and role access. Keep steps business-readable, then implement step definitions with clean automation code.
- Know Feature, Scenario, Given, When, Then, And, But, Background, Scenario Outline, Examples, Data Tables, tags, and hooks.
- Practice mapping Gherkin steps to step definitions without creating duplicate wording for the same behavior.
- Prepare an answer about when not to use Cucumber: low-level unit tests, simple API checks, and internal technical cases.
- Explain how reports, CI, and failure screenshots back connects to scenario names.
Cucumber BDD flow
If the feature file needs a developer to translate every line, it is probably too technical.
What Strong Cucumber Answers Prove
Strong Cucumber answers show that you understand BDD as a collaboration practice, not just a file format.
| Topic | Weak answer | Strong answer |
|---|---|---|
| Gherkin | Given I click button. | Given the customer has an active cart. |
| Steps | One step for every click. | Reusable behavior steps with clear implementation. |
| Hooks | Put all setup in hooks. | Use hooks for clean setup and cleanup, not hidden business flow. |
| Tags | Tag randomly. | Use tags for smoke, regression, component, or business area selection. |
Test Yourself: Cucumber Quiz
Ready to test your Cucumber knowledge?
6 questions, about 4 minutes. Score 70% or higher to earn a shareable certificate.
Frequently Asked Questions
What do Cucumber interviews usually ask?
Is Cucumber a testing tool or BDD tool?
Can Cucumber be used without Selenium?
What Cucumber project should I discuss?
What is the biggest Cucumber interview mistake?
Is there a Cucumber quiz?
Practice BDD answers with examples
Hyring's AI Video Interviewer can score whether your Cucumber answers explain behavior, examples, and trade-offs clearly. Use this page before BDD and automation framework interviews.
Try AI interview prepSources
Written by Adithyan RK