On Thu, Feb 25, 2010 at 4:44 PM, lawwantsin
wrote:
> i'm calling a very simple should_receive method on a returned instance
> and it's saying the implementation code is not calling it. i get this
> error in my specs alot. i've read the rspec beta book and it doesn't
> mention examples like this.
i'm calling a very simple should_receive method on a returned instance
and it's saying the implementation code is not calling it. i get this
error in my specs alot. i've read the rspec beta book and it doesn't
mention examples like this. i couldn't find any solutions on the
forum yet so i wanted
On Thu, Feb 25, 2010 at 1:57 PM, Sean DeNigris wrote:
> Hi,
>
> I did a bit of experimenting/Googling for what seems like a common
> operation, but didn't like what I found (mostly hand-rolled
> regexes)...
>
> I want to verify response text, but don't care about the structure.
> The text happens
Never mind, found it in the webrat specs 10 seconds after I posted...
guess it's time for a break, lol...
response.should contain 'Jim Johnson'
- Sean
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-use
Hi,
I did a bit of experimenting/Googling for what seems like a common
operation, but didn't like what I found (mostly hand-rolled
regexes)...
I want to verify response text, but don't care about the structure.
The text happens to be in a table, but appears to the user as pure
text.
E.g. table w
rogerdpack wrote:
Interesting.
It appears that with both specdoc and --format nested, it outputs the
test name *after* running it. I would have expected the opposite. Is
this expected?
Thanks.
-r
Yes. RSpec needs to know if the test passed or failed so it knows how to
color it.
At le
On Thu, Feb 25, 2010 at 11:47 AM, rogerdpack wrote:
> On Feb 25, 8:44 am, Matt Wynne wrote:
>> Do you mean --format specdoc ?
>
> Interesting.
> It appears that with both specdoc and --format nested, it outputs the
> test name *after* running it. I would have expected the opposite. Is
> this ex
On Feb 25, 8:44 am, Matt Wynne wrote:
> Do you mean --format specdoc ?
Interesting.
It appears that with both specdoc and --format nested, it outputs the
test name *after* running it. I would have expected the opposite. Is
this expected?
Thanks.
-r
__
> spec spec --format nested
Cool thanks!
-r
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
Do you mean --format specdoc ?
On 25 Feb 2010, at 15:29, rogerdpack wrote:
I'm trying to find a spec parameter that will do something like the
following
$ spec file.spec
Spec: running "it should pass spec x"
.
Spec: running "it should pass spec y"
.
That type of thing.
The use case is that
On Feb 25, 2010, at 9:29 AM, rogerdpack wrote:
I'm trying to find a spec parameter that will do something like the
following
$ spec file.spec
Spec: running "it should pass spec x"
.
Spec: running "it should pass spec y"
.
In rspec-1:
spec spec --format nested
In rspec-2;
rspec spec --for
I'm trying to find a spec parameter that will do something like the
following
$ spec file.spec
Spec: running "it should pass spec x"
.
Spec: running "it should pass spec y"
.
That type of thing.
The use case is that "one" of my tests is outputting some weird stuff
and I want to narrow down on
Thank you so much. I have been staring at this for way too long and
missed the obvious. I had a redundant active_matchers plugin that was
conflicting with shoulda.
Cheers,
Dave
On Feb 25, 1:15 am, David Chelimsky wrote:
> On Wed, Feb 24, 2010 at 2:23 AM, Dave wrote:
> > I have Rspec + Shoulda +
13 matches
Mail list logo
