Back تطوير مقاد بالسلوك Arabic Behavior Driven Development German Desarrollo guiado por comportamiento Spanish Käitumisel põhinev arendus Estonian توسعه رفتارمحور Persian Programmation pilotée par le comportement French פיתוח מונחה התנהגות HE Viselkedésvezérelt fejlesztés Hungarian Behavior-driven development Italian ビヘイビア駆動開発 Japanese

Behavior-driven development

Part of a series on
Software development
Core activities
Paradigms and models
Methodologies and frameworks
Supporting disciplines
Practices
Tools
Standards and bodies of knowledge
Glossaries
Outlines

Behavior-driven development (BDD) involves naming software tests using domain language to describe the behavior of the code.

BDD involves use of a domain-specific language (DSL) using natural-language constructs (e.g., English-like sentences) that can express the behavior and the expected outcomes.

Proponents claim it encourages collaboration among developers, quality assurance experts, and customer representatives in a software project.[1][2][3] It encourages teams to use conversation and concrete examples to formalize a shared understanding of how the application should behave.[4] BDD is considered an effective practice especially when the problem space is complex.[5]

BDD is considered a refinement of test-driven development (TDD).[1][2][6][7][vague][8] [9] BDD combines the techniques of TDD with ideas from domain-driven design and object-oriented analysis and design to provide software development and management teams with shared tools and a shared process to collaborate on software development.[2][8]

At a high level, BDD is an idea about how software development should be managed by both business interests and technical insight. Its practice involves use of specialized tools.[6] Some tools specifically for BDD can be used for TDD. The tools automate the ubiquitous language.

  1. ^ a b North, Dan (March 2006). "Introducing BDD". Dan North. Retrieved 25 April 2019.
  2. ^ a b c "Behaviour-Driven Development". Archived from the original on 1 September 2015. Retrieved 12 August 2012.
  3. ^ Keogh, Liz (2009-09-07). "Introduction to Behavior-Driven Development". SkillsMatter. Archived from the original on 2021-02-25. Retrieved 1 May 2019.
  4. ^ John Ferguson Smart (2014). BDD in Action: Behavior-Driven Development for the Whole Software Lifecycle. Manning Publications. ISBN 9781617291654.
  5. ^ Tharayil, Ranjith (15 February 2016). "Behavior-Driven Development: Simplifying the Complex Problem Space". SolutionsIQ. Retrieved 15 February 2018.
  6. ^ a b Haring, Ronald (February 2011). de Ruiter, Robert (ed.). "Behavior Driven development: Beter dan Test Driven Development". Java Magazine (in Dutch) (1). Veen Magazines: 14–17. ISSN 1571-6236.
  7. ^ Solis, Carlos; Wang, Xiaofeng (2011). "A Study of the Characteristics of Behaviour Driven Development". 2011 37th EUROMICRO Conference on Software Engineering and Advanced Applications. pp. 383–387. doi:10.1109/SEAA.2011.76. hdl:10344/1256. ISBN 978-1-4577-1027-8. S2CID 3392536.
  8. ^ a b Bellware, Scott (June 2008). "Behavior-Driven Development". Code Magazine. Archived from the original on 12 July 2012. Retrieved 1 May 2019.
  9. ^ Liz Keogh (June 27, 2011). "ATDD vs. BDD, and a potted history of some related stuff". Retrieved 6 May 2019.

Rich TVX News Network Site

Rich TVX News Network Info

© MMXXIII Rich X Search. We shall prevail. All rights reserved. Rich X Search