added some things to watch out for when doing BDD (#26408)
and a link to Dan North
This commit is contained in:
@ -56,7 +56,15 @@ Along with it are some Benefits:
|
||||
6. Resulting software design that matches existing and supports upcoming business needs.
|
||||
7. Improved quality code reducing costs of maintenance and minimizing project risk.
|
||||
|
||||
And some things to watch out for, be aware of:
|
||||
1. Beware of focusing too much on the tooling and less on the business objectives and collaboration.
|
||||
2. Be careful not to use technical details in the steps.
|
||||
3. Be careful not to focus on the implementation in the steps.
|
||||
4. BDD may not be right for every project. Consider the trade offs and choose wisely. If you automate with BDD it does, usually, add a layer of complexity. Be sure that this work is necessary to provide the benefits you hope to gain. For example, just testers using BDD probably isn't a smart way to do BDD.
|
||||
|
||||
|
||||
## More Information
|
||||
* https://dannorth.net/introducing-bdd/
|
||||
* Wiki on <a href='https://en.wikipedia.org/wiki/Behavior-driven_development' target='_blank' rel='nofollow'>BDD</a>
|
||||
* A well-known Behavior Driven Development (BDD) framework is [Cucumber](https://cucumber.io/). Cucumber supports many programming languages and can be integrated with a number of frameworks; for example, [Ruby on Rails](http://rubyonrails.org/), [Spring Framework](http://spring.io/) and [Selenium](http://www.seleniumhq.org/)
|
||||
* [BDD Guide](https://inviqa.com/blog/bdd-guide)
|
||||
|
Reference in New Issue
Block a user