TDD != BDD
Tools
* Ms Test
* Home Grown
* NUnit
* MSpec
* MBUnit
Styles
* Given/When/Then
* Context/Specification
Granularity
User Focused
Observable Behavior
When?
Crock |
Not Crock |
Changing Terms |
Acceptance / Business Requirements |
|
Context, Not S.U.T. Focused |
|
|
Pain Text, not really "Plain"
BDD can be used for low level framework development, but requires a different train of thought and context.
Allows a focus on what/why it is being built, not how it is being built.
Value in having QA that can read the tests and easily identify missing scenarios and understand what it should do
How does old style "Acceptance Tests" vary from BDD?
Could stub out tests and identify acceptance prior to writing the code that implements it. Identify that the correct thing is going to be done.
the purpose of an acceptance test/customer test, is to provide an excuse for developers and testers and customers to figure out what the application should do.
Requirements for doing it: Common language/grammer,
Whether or not doing TDD or BDD, having the tests organized by context is an indication of good testing.
BDD is a style and a mindset shift
When you start, don't start with using frameworks. Roll your own to then understand and appreciate what the tool does.
BDD helps GlennB the most because it allows him to capture the intent and how he arrived at something. Why was he thinking the thing that he was and how/why does the design solve the problem.
Comments (0)
You don't have permission to comment on this page.