search for: step_match

Hi all, I committed a first cut at blockless Givens/Whens/Thens to RSpec''s trunk: cd /path/to/rspec/project svn up cd rspec bin/spec examples/story/calculator.rb Take a look at examples/story/calculator.rb to see what''s going on. Needs docs!!!! Thoughts welcome. I''ve also got a cut at the plain text parser checked in, but it''s not hooked up to anything

...nly affects people who have bravely begun to experiment with the 2 day-old plain text story runner and definable groups of steps. For those who fit that bill, I just committed a few changes that will require you to make changes to your code. The StepMatchers class is now the StepGroup class. The step_matchers methods on PlainTextStoryRunner and StepGroup is now just steps. So instead of defining a group like this: # old - no longer supported matchers = StepMatchers.new do step_matchers do |add| add.given(...) {...} end end # new steps = StepGroup.new do steps do |add| add.given(...) {...

...tring) throws java.lang.Exception:in `/I am on the (Google|yahoo) search page/'' You can run again with --guess to make Cucumber be more smart about it (Cucumber::Ambiguous) /opt/jruby-1.2.0/lib/ruby/gems/1.8/gems/cucumber-0.2.3/bin/../lib/cucumber/step_mother.rb:122:in `step_match'' /opt/jruby-1.2.0/lib/ruby/gems/1.8/gems/cucumber-0.2.3/bin/../lib/cucumber/ast/step_invocation.rb:50:in `find_step_match!'' Infact I am getting the same error whenver I try to run more than one scenario in a feature file with java step definitions. But running the same via...

I think we all know that the readability of steps isn''t great right now, and in fact there''s a very recent thread that discusses just that. It was that recent thread that prompted me to explore this a bit. The basic idea is that you define step matchers, which have a regex, and then you match step names against that regex. Kind of tough for me to explain so I''ll just