Lesson 1 of 88 min read
Decide what BDD is for on your team
Foundation 1: Behaviour-Driven Development is a collaboration practice first and a tool second. Product, development and QA agree on concrete examples of a rule before code exists; Cucumber then turns some of those examples into executable checks. Our synthetic Cart has three rules: a 10-1 quantity limit, a SAVE10 coupon and free shipping from 999 rupees after discount. A feature file that nobody outside QA reads is just a verbose test script. Keep unit tests for arithmetic edge cases and use Gherkin where shared language helps. Passing scenarios prove the examples they contain, not every rule in the product. Start with a short boundary note before adding tooling. This free orientation uses a synthetic shopping cart; it does not run Maven or a browser inside the website.
Key takeaways
- 1Identify the business rule and a concrete example.
- 2Write an observable expectation and an excluded claim.
- 3Keep proposed deployment work distinct from performed checks.
Synthetic boundary note
Rule: coupon SAVE10 takes 10% off the subtotal Example: lamp 899 + mug 249, coupon -> discount 114.80, total 1033.20 Not here: payment, browser layout, performance
Go deeper
Expert notes beyond the basics
- 01
Reason through the boundary
Behaviour-Driven Development is a collaboration practice first and a tool second. Product, development and QA agree on concrete examples of a rule before code exists; Cucumber then turns some of those examples into executable checks. Our synthetic Cart has three rules: a 10-1 quantity limit, a SAVE10 coupon and free shipping from 999 rupees after discount. A feature file that nobody outside QA reads is just a verbose test script. Keep unit tests for arithmetic edge cases and use Gherkin where shared language helps. Passing scenarios prove the examples they contain, not every rule in the product.
- 02
Official reference
Cucumber documentation: https://cucumber.io/docs/ . Use installed-version guidance and actual evidence, not assumed deployment results.
Common mistakes to avoid
- - Writing UI click steps instead of business behaviour.
- - Sharing scenario state through static fields.
Try it yourself
Write a rule, action, evidence and limitation for this topic.
Write your answer on paper or in a sheet first, then compare.
Interview questions
How to answer like a confident QA engineer
- Q1
What is BDD primarily?
Model answer
A collaboration practice using concrete examples
- Q2
What is outside this check?
Model answer
Functional correctness, real permission security, performance and deployed-version history need separate evidence.
Knowledge check
+5 points
What is BDD primarily?
