Did any of you use behavior driven development in your projects?
The concept and tools for it sound great. But was it easy to introduce and then stick to it? Did it lead to significant and visible positive results?
Software Engineering Stack Exchange is a question and answer site for professionals, academics, and students working within the systems development life cycle. It only takes a minute to sign up.Sign up to join this community
Yes. Used it.
Yes. Stuck to it. It was easy. All behaviors were provided by examples. No narrative text "specifications". Actual examples with actual business rationale. Since users can do this, there are no intermediary business analysts.
Yes. Without it, some bunch of business analysts would still be writing contradictory and incomplete "specifications" for the software design. With it, the users described what should happen specifically. Concrete real-world examples of behavior.
I turned the examples into unit tests. Code was written to pass the tests.
It's pretty simple once you start doing it.
If you have any idea on what you want your program to do (high level, low level, whatever), formalize it into a test before you start writing code.
'When I open the program I should see option X, Y, and Z'
Formalize it into test code. Write the code. Voila.