8.3. Expressive power with BDD tools
BDD was born out of certain TDD practitioners looking for a better vocabulary to describe the intent of the tests written as part of the TDD cycle. The word test didn’t quite capture the spirit of specifying desired behavior and it carries a lot of connotations. Instead, the community started talking about specifications (or just specs) and behavior rather than tests and test methods.
As a side effect of looking for a better vocabulary, the BDD community wrote a bunch of handy alternatives to established test frameworks like JUnit. Aside from helping you steer clear of the muddy waters of testing when you’re really specifying desired behavior, these tools tend to highlight the test’s intent and fade the syntax ...
Get Effective Unit Testing now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
