We found that we can raise a Cucumber::Pending error in the step
matcher to achieve the same effect, though in practice we're tending
to just write PENDING in the feature and break the link to the step
matcher.
Actually something that would really help us is the ability to
comment out scenarios, as you quite often have code you want to check
in but you don't want to break the build due to a half-finished
feature. I'm finding I spend a lot longer between check-ins since I
started using cucumber in earnest, and that can't be a good thing.
Maybe just altering that behaviour where the scenario carries on
running when a Given step fails would help. Aslak you never explained
why you designed it like that - how does it help with your workflow?
On 17 Sep 2008, at 02:20, David Chelimsky wrote:
On Tue, Sep 16, 2008 at 8:16 PM, Scott Taylor
<[EMAIL PROTECTED]> wrote:
Shouldn't pending 'a message' work in cucumber? Is this a bug?
Currently
it's raising Rspec's PendingExpectationError.
This came up last week:
http://groups.google.com/group/rspec/browse_thread/thread/
84743f0ef89a82f/
Didn't really get resolved.
Go ahead and put a ticket in lighthouse if you want (under cucumber
project: http://rspec.lighthouseapp.com/projects/16211).
Cheers,
David
SCott
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
cheers,
Matt
----
http://blog.mattwynne.net
http://songkick.com
In case you wondered: The opinions expressed in this email are my own
and do not necessarily reflect the views of any former, current or
future employers of mine.
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
