Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Test-driven development
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
=== TDD and BDD === BDD ([[behavior-driven development]]) combines practices from TDD and from ATDD.<ref>{{cite web |title=BDD |url=http://guide.agilealliance.org/guide/bdd.html |access-date=2015-04-28 |archive-date=2015-05-08 |archive-url=https://web.archive.org/web/20150508045550/http://guide.agilealliance.org/guide/bdd.html |url-status=dead }}</ref> It includes the practice of writing tests first, but focuses on tests which describe behavior, rather than tests which test a unit of implementation. Tools such as [[JBehave]], [[Cucumber (software)|Cucumber]], [[Mspec]] and [[Specflow]] provide syntaxes which allow product owners, developers and test engineers to define together the behaviors which can then be translated into automated tests.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)