Cucumber / BDD for QA: where it is used, what it pays, how to learn it
Cucumber is a behaviour-driven development tool that runs plain-language scenarios written in Gherkin. Each step maps to code, so specifications double as automated tests. 257 of the 4,012 QA listings we track mention it, about 23% of them remote. Posted pay for those listings has a median of $111k a year.
Middle half $94k to $130k, from 26 listings with a published range.
What Cucumber / BDD is used for in QA
Cucumber is a behaviour-driven development tool that runs plain-language scenarios written in Gherkin. Each step maps to code, so specifications double as automated tests.
- Turning acceptance criteria into executable scenarios the whole team can read.
- Sharing a single set of scenarios between product, QA and development.
- Generating living documentation from passing scenarios.
- Driving UI or API automation with a business-readable layer.
Top countries in our listings
- United States61
- India52
- United Kingdom14
Which roles use Cucumber / BDD
Pay is the US median for a mid-level hire. Other levels and countries are on each role's page.
None of our 15 role profiles lists Cucumber / BDD as a core tool. Employers add it as a plus on bdd work.
Listings that mention Cucumber / BDD
Quality Assurance Analyst
SDET - Automation Testing
Senior Test Analyst - Automation
SDET
QA Automation (Selenium/Java)
SDET I
Learn Cucumber / BDD in five steps
A practical order that gets you to a working project. Build something at each step; reading alone does not stick.
- 1
Learn Gherkin
Write Feature, Scenario, Given, When, Then, Background and Scenario Outline with Examples.
- 2
Bind steps to code
Implement step definitions in Java, JavaScript or another language.
- 3
Write declarative scenarios
Describe behaviour, not clicks, and keep each scenario to one rule.
- 4
Organise and reuse
Use tags, hooks and shared world state; keep step libraries small.
- 5
Run and report in CI
Execute by tag in the pipeline and publish the HTML or JSON report.
Cucumber / BDD vs Robot Framework
| Aspect | Cucumber / BDD | Robot Framework |
|---|---|---|
| Syntax | Gherkin sentences | Keyword tables |
| Intended owner | Whole team, including product | Test engineers |
| Risk | Step bloat and UI-flavoured scenarios | Keyword sprawl |
| Languages | Java, JavaScript, Ruby, C# and others | Python core |
Choose Cucumber / BDD when
Product and QA genuinely review scenarios together before building.
Choose Robot Framework when
Only testers read the tests and you want a mature built-in report.
Interview questions about Cucumber / BDD
Questions from our Interview Vault that test Cucumber / BDD knowledge. Answer aloud first, then reveal the model answer.
How do you write a good Gherkin scenario?
Keep it declarative and about one behaviour: Given a context, When a single action, Then an observable outcome. Avoid UI mechanics such as clicking a blue button, use Examples tables for variants, and write it so a business reader can confirm it.
Business / Test Analyst · Mid · BDD
How strong is your Cucumber / BDD experience on paper?
Run your CV through the checker for Cucumber / BDD keywords and results, or take the 10-minute level test.
Cucumber / BDD FAQ
Is Cucumber worth the overhead?
Only if business people read and write scenarios. If only engineers touch them, the Gherkin layer adds cost without value and plain test code is simpler.
Can Cucumber test APIs?
Yes. The steps call any code, so scenarios can drive HTTP clients as easily as a browser.
How much do jobs that ask for Cucumber / BDD pay?
Listings that mention Cucumber / BDD and publish a pay range have a median of about $111k a year in USD terms (middle half $94k to $130k, from 26 posted ranges).
Which QA roles use Cucumber / BDD?
No role in our set lists Cucumber / BDD as a core tool, so it usually appears as an extra skill.