On 10/15/07, David Chelimsky <[EMAIL PROTECTED]> wrote: > Having this expression of stories and scenarios appearing devoid of > programmatic ideas has great potential to help the customers feel > ownership over stories/scenarios. Of course, there is an underlying > relationship to syntax that they'd have to understand and, ideally, > the system would help them out with (i.e. if they do write a new > scenario with steps that don't match any existing steps, they'd be > alerted). But that's all a bit down the road. > > Thoughts?
I for one really like where this seems to be heading. Reminds me much of a php project with similar ambitions called Arbiter, http://arbiter.sf.net. What's nice about this, is the customer plays a hand in defining what the syntax is, deepening the buy in since I can conceivably write matchers to work with the language the customer uses rather than attempt to constrain them into using a new vocabulary. I haven't read all the posts in detail or given Pat's pasties a thorough study but I'd assume there would/could also be a non-match catch all matcher that could be used to identify steps that appear to require a new matcher or perhaps needing to be reworded, etc. ? -Mike _______________________________________________ rspec-users mailing list rspec-users@rubyforge.org http://rubyforge.org/mailman/listinfo/rspec-users
