benchmarkstt
benchmarkstt copied to clipboard
Behaviour driven development
(related to #14 and #21 )
It seems like it would be a good idea, but needs some enthusiasm from all parties involved, developers and analysts/stakeholders. If developers are willing to aid analysts in writing correctly formatted specifications in the dialect of the chosen BDD, and implement these, and equally the analysts are willing to learn and keep to the newly learned BDD dialect, then it could increase our overall efficiency, as well as create clarity to the proceedings.
Speaking for the "analysts" I'm completely in favour and willing to adapt to whatever dialect we choose. I have experience of Cucumber.
Action before closing: add BDD for release 1.