Talk:Behavior-driven development
Let's talk about it before speedily deleting this article again... I'm sorry the first version was so information free... I just wanted to create a space to discuss the topic.
I've updated the article. Maybe the context message can go now.
The message can't go! The article, especially the beginning, is in terrible condition. --Mislav 22:04, 12 October 2006 (UTC)
Dave Astels
Dave Astels also influences BDD. See his ideas and framework (at the moment in Ruby) in this video: Beyond Test Driven Development - Behaviour Driven Development ( 302 MB, 47:40 min ) Google TechTalks March 17, 2006 [1]. --Erkan Yilmaz 20:31, 11 November 2006 (UTC)
I'm dubious about the accuracy of this article. Many of the things it says about BDD are things I thought were already true of test-driven development. Needs more cites. — Preceding unsigned comment added by 24.6.102.150 (talk) 01:02, 18 March 2007 (UTC)
What is the relationship with traditional specification as language (CLU, Eiffel)?
Consider representation invariants in a language such as CLU, or invariants in design-by-contract as in Eiffel.
These methods of development are similar to Behavior Driven Development. First one creates a specification for behavior, then the implementation of that behavior. The difference seems to be that there is less danger of destroying encapsulation when the specification is only for externally visible behavior. That is, the behavior of encapsulated details should be private, and should not require making those details public.
Has anyone written about the parallel between classic "executable specification" and Behavior Driven Development? Should something go in this article? --Frank Hileman 22:14, 26 September 2007 (UTC)