[Cucumber] --dry-run


#1

Hi Guys,

I see in the Cucmber --help that -d akd --dry-run is supported but it
doesn’t seem to work.

Anyone know why?

Thanks, very much.

Tim


#2

On Mon, Feb 2, 2009 at 7:00 PM, Tim W. removed_email_address@domain.invalid wrote:

Hi Guys,

I see in the Cucmber --help that -d akd --dry-run is supported but it
doesn’t seem to work.

Anyone know why?

Because it has a bug that has been fixed in 0.2 prereleases (0.1.99.x)
http://tinyurl.com/cucumber-0-2-beta

Aslak


#3

On Feb 2, 2009, at 6:30 PM, Ben G. wrote:

 ex.responses.should be_nil
 ex.responses.should_include @auth_response
 ex.responses.include?.with('a').should be_true

end

Clearly, it makes no sense. Somehow the exception validation block
is not running. What am I doing wrong?

raise_error doesn’t take a block, and so it’s being ignored:

http://rspec.rubyforge.org/rspec/1.1.12/classes/Spec/Matchers.html#M000483

Scott


#4

Hi all,

This spec always passes:

 lambda do
   process_card @credit_card, billing_info, 10604, '1.1.1.1', 

@gateway
end.should raise_error(MinimalCart::CaptureFailureError) do |ex|
ex.should be_nil
ex.should_not be_nil
ex.responses.should be_nil
ex.responses.should_include @auth_response
ex.responses.include?.with(‘a’).should be_true
end

Clearly, it makes no sense. Somehow the exception validation block is
not running. What am I doing wrong?

Thanks
Ben


#5

On Mon, Feb 2, 2009 at 3:30 PM, Ben G.
removed_email_address@domain.invalid wrote:

 ex.responses.should_include @auth_response
 ex.responses.include?.with('a').should be_true

end

Clearly, it makes no sense. Somehow the exception validation block is not
running. What am I doing wrong?

try using { } instead of do…end. Pretty sure that the problem you’re
experiencing has to do with Ruby’s block precedence.

Pat


#6

On Feb 2, 2009, at 6:30 PM, Ben G. wrote:

 ex.responses.should be_nil
 ex.responses.should_include @auth_response
 ex.responses.include?.with('a').should be_true

end

Clearly, it makes no sense. Somehow the exception validation block
is not running. What am I doing wrong?

Disregard my last email. I was being stupid.

Scott


#7

Hi all,

This spec always passes:

 lambda do
   process_card @credit_card, billing_info, 10604, '1.1.1.1', 

@gateway
end.should raise_error(MinimalCart::CaptureFailureError) do |ex|
ex.should be_nil
ex.should_not be_nil
ex.responses.should be_nil
ex.responses.should_include @auth_response
ex.responses.include?.with(‘a’).should be_true
end

Clearly, it makes no sense. Somehow the exception validation block is
not running. What am I doing wrong?

Thanks
Ben


#8

On Mon, Feb 2, 2009 at 4:22 PM, Pat M. removed_email_address@domain.invalid wrote:

 ex.should_not be_nil
 ex.responses.should be_nil
 ex.responses.should_include @auth_response
 ex.responses.include?.with('a').should be_true

end

Clearly, it makes no sense. Somehow the exception validation block is not
running. What am I doing wrong?

try using { } instead of do…end. Pretty sure that the problem you’re
experiencing has to do with Ruby’s block precedence.

oops I should have been more specific. I meant use { } for the block
after raise_error:

lambda do
process_card @credit_card, billing_info, 10604, ‘1.1.1.1’, @gateway
end.should raise_error(MinimalCart::CaptureFailureError) { |ex|
ex.should be_nil
ex.should_not be_nil
ex.responses.should be_nil
ex.responses.should_include @auth_response
ex.responses.include?.with(‘a’).should be_true
}

Although I think that do…end.method is hideous and so I would change
the lambda to use curly braces as well :slight_smile:

Pat