search for: etec

...aintenance changes may be a pain when you have to add or remove fields. Additionally, the declarative version removes all of the noise so that the most important features of that story stand out. The imperative version looks like the "detailed scenarios" that David talked about at his ETEC slides (http://blog.davidchelimsky.net/articles/2008/04/01/etec-slides.) On slide #75 David gives a good overview of the pros and cons of this style. The pros mentioned are that they are easier to write and easier to change. While my stories may not read quite as bad as the example presented...

Hey list, I''m refactoring some much-used functionality into a common_steps step group. Methods like this are in there: steps_for :common do Given "a number of existing $types?" do |type| @initial_item_count = type.singularize.classify.constantize.count end When "the user adds an invalid $type" do |type| post