Jon Swanson wrote:
Is there anything about BDD that might be appealing specifically to the people that specify requirements (or not) beyond the arguments in favor of test-driven development?
Burk Hufnagel wrote:Does that seem reasonable?
Burk Hufnagel wrote:
Unit tests (for TDD) and specifications (for BDD) are different in that specifications are at a higher level of abstraction.
Ashish Dutt wrote:This is what i would like to know, how can BDD help me to model the intention of the user?
But what confounds me now is, how will i model and test the "intention" of the user in the light of BDD approach with Javascript?
Burk Hufnagel wrote:
Which reminds me, some testing frameworks allow the author to tag a test and then just run the tests with that tag - so you can have tests tagged with labels like '@Fast', or '@Slow-DB', so the test runner can run a subset of the test suite then (if those tests passed) run the rest of the suite. Does Jasmine support that? If not, are you aware of another framework that might?
Burk Hufnagel wrote:The article sounds interesting - could you supply a link to the magazine's site?
Surfing the web, there seems to be vareity of tools out there for BDD. Are you weighing them or prefer one over the other ? Any recommendations in your book ?
BDD means understanding how the program is supposed to behave