If your code uses Date#now, always make sure you stub it in your
specs. Always.
On 5. mai. 2008, at 05.42, "s.ross" <[EMAIL PROTECTED]> wrote:
Hi--
On May 3, 2008, at 9:17 AM, Joe Van Dyk wrote:
I occasionally get this error:
1)
'A puzzle once featured, should no longer be nominated' FAIL
Hi--
On May 3, 2008, at 9:17 AM, Joe Van Dyk wrote:
I occasionally get this error:
1)
'A puzzle once featured, should no longer be nominated' FAILED
expected: Sun May 04 09:10:26 -0700 2008,
got: Sun May 04 09:10:26 -0700 2008 (using ==)
./spec/models/puzzle_spec.rb:180:
So, the dates l
I've never tried to use them myself, but another list member brought
this up in another thread.
He was using a message expectation in a story step, and couldn't get it to fail.
Looking at what he was doing, it didn't look to me that it would ever
succeed, which got me thinking.
Message expectati
I am and I will
On 4-May-08, at 12:30 PM, Matt Berther wrote:
rspactor
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
Hi Andrew,
I've been using rspactor (the command line version) and really prefer
it to autotest. If you're using a Mac, you may want to look at this.
--
Matt Berther
http://www.mattberther.com
On May 3, 2008, at 1:36 PM, Andrew Brown wrote:
I will, once I resolve the error.
On 3-May-0
Hi Rick - Thanks again.
Cool - I see what you mean about what the story steps should get
involved with, and what should be left to the specs.
In that case, my response.should have_tag('li', @title) is a
reasonable test, and I'll leave it at that!
All the best,
Steven
On Sun, May 4, 2008 at 3:36 PM
On Sun, May 4, 2008 at 10:16 AM, steven shingler <[EMAIL PROTECTED]> wrote:
> Hi Rick,
> Thanks for your reply.
> You are right that this step is basically testing the basic actions of
> a controller, and is being run as part of a story_with_steps stack.
> The step itself is definitely being hi
Hi Rick,
Thanks for your reply.
You are right that this step is basically testing the basic actions of
a controller, and is being run as part of a story_with_steps stack.
The step itself is definitely being hit, because I have a:
response.should have_tag('li', @title)
...in the same step, and that
