> > I was working on a past project tonight to trunk which is using the > > old story format. IE: > > Given "desc" do / end > > When "someting "do /end > > etc.. > > > > Is this officially supported, or is this just something that hasn't > > been ripped out yet? > > It's funny to me that this is "Old Style" in your view. It's really > just another approach. Plain text is great for some situations, but so > is writing in Ruby :) Depends on the team, really, and how involved > the customer is in actually doing the typing. > > > If it is officially supported how attached are people to the re-using > > of do/end blocks which match the same description. Every now and then > > it bites me and I end up having to change one of the descriptions to > > differ textually then another. > > Why would this be specific to scenarios written in Ruby? > > > IMO it is kind of annoying. A story > > part description may have the same description as another in the same > > scenario. Sometimes the sequence of steps provide the context,
If I understand you correctly, then we had a discussion on this: http://rspec.lighthouseapp.com/projects/5645/tickets/167-blocks-provided-to-when-then-clauses-should-always-be-used and concluded that same-description means exactly-same-step, then continued http://rspec.lighthouseapp.com/projects/5645/tickets/172-warn-or-fail-on-re-specified-when-then-clause which is still open. > This seems unfinished - was there more to this sentence? > > I think this is just a matter of documentation. If we got rid of > block-sharing we'd be promoting much more verbose scenarios with a lot > of redundancy. I think it's here to stay. _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
