On Mon, May 4, 2009 at 5:17 PM, jfrankov wrote:
> I have a step definition file where I'm saving a model object and want
> to use this syntax (it's common, I see it in examples everywhere):
>
> Event.should have(1).record
This is an rspec-rails extension of ActiveRecord. It's not cucumber
(or rsp
I have a step definition file where I'm saving a model object and want
to use this syntax (it's common, I see it in examples everywhere):
Event.should have(1).record
...but it gives this error:
undefined method `record' for # (NoMethodError)
Am I missing some library or require or something? I
I wonder if anyone has some clues as to what is happening in the
following..
Output from running the feature..
Quote>>
Scenario: Create an Order
Given I'm viewing the Rubber Duck product
When I press "Add to cart"
Then I should see "Rubber Duck"
When I press "Checkout"
Then I should see "Checkou
On Mon, May 4, 2009 at 1:57 PM, BJ Clark wrote:
> Fernando,
>
> They are easier to spec with Pat Maddox's "no peeping toms" plugin.
> http://github.com/pat-maddox/no-peeping-toms/tree/master
I use Pat's no-peeping-toms plugin as well. It's a great tool in Rails toolbox.
Brandon Keepers has made
On Mon, May 4, 2009 at 10:57 AM, BJ Clark wrote:
> Fernando,
>
> They are easier to spec with Pat Maddox's "no peeping toms" plugin.
> http://github.com/pat-maddox/no-peeping-toms/tree/master
>
FWIW, I was not able to run specs surrounded by a with_observer call when
using mislav-will_paginate.
Fernando,
They are easier to spec with Pat Maddox's "no peeping toms" plugin.
http://github.com/pat-maddox/no-peeping-toms/tree/master
BJ Clark
On May 4, 2009, at 5:33 AM, Fernando Perez wrote:
Hi,
Before I do anything stupid, I'd like to know if there are any gotchas
when using Rails obser
Aslak Hellesøy wrote:
>
> Then that's a case for better documentation - not more Cucumber
> features.
> Feel free to create a separate Wiki page for "plain ruby" projects that
> points the user to newgem and jeweler.
Actually, that was what I was doing when I first raised the question.
--
Post
Hi,
Before I do anything stupid, I'd like to know if there are any gotchas
when using Rails observers instead of writing my own methods or
callbacks? Are they easy to spec/test or will I run into troubles? Are
they easily mockable?
--
Posted via http://www.ruby-forum.com/.
___
I followed Bryan's pattern here, and let RSpec reset everything.
http://www.brynary.com/2009/2/3/cucumber-step-definition-tip-stubbing-time
On May 4, 2009, at 3:13 AM, aslak hellesoy wrote:
One thing to be aware of when stubbing: There is no cleanup/revert
logic yet in Cucumber. This means
> On Sun, May 3, 2009 at 10:42 PM, Mike Doel wrote:
>
>>
>> I also make use of FakeWeb in a couple places to do a similar thing for
>> the scraping of sites.
>
>
> FWIW, so does the maintainer of FakeWeb, Chris Kampmeier (with whom I
> work).
>
> Stubbing should be avoided when using Cucumber, if
It's possibly worth pointing out for anyone else who needs to do
stubbing, that you don't necessarily need a framework to stub stuff; I
have cucumber tests that stub out some setup code in my app*, and they
just use monkey-patching to do the stubbing.
For instance, in the example below, you could
On Sun, May 3, 2009 at 10:42 PM, Mike Doel wrote:
>
> I also make use of FakeWeb in a couple places to do a similar thing for the
> scraping of sites.
FWIW, so does the maintainer of FakeWeb, Chris Kampmeier (with whom I work).
Stubbing should be avoided when using Cucumber, if only because th
12 matches
Mail list logo
