BDD stands for "Behavior-Driven Development," a software development style that encourages cooperation between developers and stakeholders through identifying and exploring different examples of how a system or smaller element of code might work from a user's perspective.

learn more… | top users | synonyms

5
votes
6answers
1k views

What are the advantages to BDD for a solo developer?

I have found this lines below about the advantages of BDD (Behavior Driven Development) The domain experts define what they need in the program in a way that the developers can not misinterpret ...
2
votes
2answers
377 views

How do you end up with event-sourcing if you use a xDD approach?

When working in a TDD or BDD manner your unit tests are supposed to drive your design. But how do you end up with event-sourcing using a xDD techniques? As I see it event sourcing is something you ...
6
votes
2answers
527 views

BDD to replace the test teams work - how best to do it?

The system we are developing, using .NET, is extremely large, complex, and some modules are poorly written. We have a large user acceptance test team that is aiming for 100% business scenario ...
6
votes
2answers
677 views

Are there any companies using BDD in a .NET environment?

I've seen BDD in action (in this case using SpecFlow and Selenium in a .NET environment) for a small test project. I was very impressed - mainly due to the fact that the language used to specify the ...
11
votes
2answers
916 views

Relation between BDD and TDD

What is the relation of BDD and TDD? From what I understood BDD adds two main things over TDD: tests naming (ensure/should) and acceptance tests. Should I follow TDD during development by BDD? If ...
5
votes
2answers
477 views

Testing-related methodologies except TDD/BDD [closed]

Are there any testing-related methodologies except TDD/BDD? I see a lot of people who practice their own testing approaches (e. g., see Ayende post), but I don't see any formalization for it, no ...
3
votes
2answers
231 views

Product Owner and automated tests

One of the claims of BDD-style development is that it bridges the gap between Product Owner and developers: the Product Owner writes a story, which can be converted in an equivalent automated test ...
3
votes
2answers
336 views

Using automated bdd-gui-tests to keep user-documentation-screenshots up do date?

Are there developpers out there, who (ab)use the CaptureScreenshot() function of their automated gui-tests to also create uptodate-screenshots for the userdocumentation? Background: Whithin the ...
0
votes
1answer
237 views

What is the scope of a Bdd Scenario particularly when specifying changes to an existing application?

We have been working with BDD for sometime now and one issue that keeps cropping up is related to the scope of our scenarios. Particularly when it come to making a change to existing functionality. ...
7
votes
5answers
1k views

What is the role of QA in a BDD-driven project?

If running a project using BDD with 100% coverage of user stories with automated acceptance tests, what would be the role of a tester / quality assurance person? I guess I am imagining that ...
2
votes
3answers
221 views

Is it practical to retroactively write specifications documenting a system via automated acceptance tests?

If a project was coded without much (or any) formal documentation and is without unit tests, does it make any sense to use tools like Fitnesse and SpecFlow to write automated acceptance tests as the ...
18
votes
7answers
1k views

TDD/Tests too much an overhead/maintenance burden?

So you've heard it many times from those who do not truly understand the values of testing. Just to start things out, I'm a follower of Agile and Testing... I recently had a discussion about ...
6
votes
2answers
256 views

Behaviour driven development IRL [closed]

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 ...
7
votes
5answers
653 views

BDD/TDD vs JAD?

I've been proposing that my workplace implement Behavior-Driven-Development, by writing high-level specifications in a scenario format, and in such a way that one could imagine writing a test for it. ...