Talk:Behavior-driven development: Difference between revisions

Content deleted Content added
"SHE QC" and "The Three Amigos": agree - removed - removed Example Mapping as well with same concerns
Line 94:
 
Reading the article it suggests that the key drivers for BDD are the stakeholders but typically they are totally clueless about everything outside the business ___domain. For example if you want to use TDD on non-business ___domain units such as form or graphics composition libraries interopability libraries import export libraries application frameworks or pretty much any other component developed that is generic enough to satisfy a projects architecture - why would you even want to come up with a convaluted warping of a user story to somehow justify reading or writing a byte of data somewhere or another? ZhuLien [[Special:Contributions/66.249.80.203|66.249.80.203]] ([[User talk:66.249.80.203|talk]]) 16:13, 5 March 2014 (UTC)
: Indeed, the approach explained in the main article lacks sections on its scope, criticism. Can the approach itself be falsified to show its limits? If this concern is disregarded by the proponents of BDD, they look more like prophets than scientists. --[[User:Ilgiz|ilgiz]] ([[User talk:Ilgiz|talk]]) 09:51, 29 February 2020 (UTC)
 
== External links modified ==