Ok I think I've figured out the command that makes rspec blow up.
I'm creating the mock object like this:
def prepare_order_mock
$GCHECKOUT_FRONTEND = mock "gcheckout"
@co_cmd_mock = mock "checkout_command"
@shopping_cart = mock "shopping cart"
@private_data = nil
$
On Tue, 2008-02-05 at 23:50 -0500, Will Schenk wrote:
> This is both running the file directly or using script/spec. If I
> leave the spec file as is, and I comment out a line
> @order.send_order_to_google_checkout in the _controller_ then it runs
> fine, i.e. it gets to the fail statement.
Since
This is both running the file directly or using script/spec. If I
leave the spec file as is, and I comment out a line
@order.send_order_to_google_checkout in the _controller_ then it runs
fine, i.e. it gets to the fail statement. Either way the code runs
all the way through the action met
That seems more like rspec isn't even finding it. What is the file name? Is
it in a location that rspec is going to look for it?
-Corey
On Feb 5, 2008 4:58 PM, Will Schenk <[EMAIL PROTECTED]> wrote:
> I've been beating my head against this for a couple of hours now, and
> I'm a bit frustrated, s
I've been beating my head against this for a couple of hours now, and
I'm a bit frustrated, so I apologize in advance.
I'm trying to use rspec to test an order processing system, which uses
google checkout. The idea was to have a couple of orders in the
database in various stages, and hit t
