Content deleted Content added
→TDD wrongly represented?: new section |
|||
Line 84:
Does anyone object to changing this to represent TDD better, do you feel that saying "essentially states" prevents this from being an oversimplification? [[User:Oliver Gramberg|Oliver Gramberg]] ([[User talk:Oliver Gramberg|talk]]) 08:09, 27 February 2014 (UTC)
== Business and Stakeholder driven via User Stories / BDD useful only for high-level business ___domain logic? ==
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)
| |||