On Mon, Jun 2, 2008 at 11:23 PM, Jose Fernandez <[EMAIL PROTECTED]> wrote:
> Pat Maddox wrote:
>> On Mon, Jun 2, 2008 at 11:16 PM, Jose Fernandez <[EMAIL PROTECTED]>
>> wrote:
>>> So how can I test a mocked rails controller within my plugin's specs?
>>
>> I don't quite follow you. Can you post an
Pat Maddox wrote:
> On Mon, Jun 2, 2008 at 11:16 PM, Jose Fernandez <[EMAIL PROTECTED]>
> wrote:
>> So how can I test a mocked rails controller within my plugin's specs?
>
> I don't quite follow you. Can you post an example of what you're trying
> to do?
>
> Pat
http://github.com/jfernandez/s
On Mon, Jun 2, 2008 at 11:16 PM, Jose Fernandez <[EMAIL PROTECTED]> wrote:
> So how can I test a mocked rails controller within my plugin's specs?
I don't quite follow you. Can you post an example of what you're trying to do?
Pat
___
rspec-users mailin
So how can I test a mocked rails controller within my plugin's specs?
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On Mon, Jun 2, 2008 at 11:09 PM, Jose Fernandez <[EMAIL PROTECTED]> wrote:
> I can't figure out how to build rspec-rails as a gem when just cloned
> from github... there isn't any .gemspec file or rake task that does
> this. Any help?
rspec-rails is a rails plugin, not a gem.
Pat
I can't figure out how to build rspec-rails as a gem when just cloned
from github... there isn't any .gemspec file or rake task that does
this. Any help?
--
Posted via http://www.ruby-forum.com/.
___
rspec-users mailing list
rspec-users@rubyforge.org
htt
On Mon, 2008-06-02 at 14:52 -0600, Ben Mabey wrote:
> David Chelimsky wrote:
> > Did that work? I'm not able to check this minute, but I recall a bug
> > w/ rspec/rails/stories.
> >
>
> Yes, there was a bug that prevented it before. I believe this was
> resolved some time ago with a commit by
Ben Mabey wrote:
>
> I don't have time to parse your entire post or send a lengthy reply.
> However, this blog post walks through how to do exactly what you are
> attempting:
> >http://www.glennfu.com/2008/03/31/easy-plaintext-stories-in-ruby-on-rails-using-webrat/
I wrote the login "Given" claus
Ben Men wrote:
I've been slamming my head against a wall for a while now, and would
like some help. I believe this is session related.
I have a story that looks like:
--
Given that a post exists
And I am logged in
When I visit the po
I've been slamming my head against a wall for a while now, and would
like some help. I believe this is session related.
I have a story that looks like:
--
Given that a post exists
And I am logged in
When I visit the post details page
Steve Downey wrote:
I have specs that ran fine in Rails 2.02/RSpec 1.13 that are failing
on Rails 2.1/RSpec 1.14.
There is one problem and one issue:
problem: sometimes (but not always) I get a NoMethodError referencing
a has_many association
issue: in helper specs, instance variables don't
David Chelimsky wrote:
On Jun 2, 2008, at 12:20 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
Ben Mabey wrote:
The spec command is just for specs. Although the story runner now uses
the same command line option parser. So you can pass in the args when
running your runner file. Like so:
ruby st
On Jun 2, 2008, at 12:20 PM, Matt Wynne <[EMAIL PROTECTED]> wrote:
Ben Mabey wrote:
The spec command is just for specs. Although the story runner now
uses
the same command line option parser. So you can pass in the args
when
running your runner file. Like so:
ruby story.rb -f=html
or th
I have specs that ran fine in Rails 2.02/RSpec 1.13 that are failing on
Rails 2.1/RSpec 1.14.
There is one problem and one issue:
problem: sometimes (but not always) I get a NoMethodError referencing a
has_many association
issue: in helper specs, instance variables don't get set unless the
Helpe
Ben Mabey wrote:
> The spec command is just for specs. Although the story runner now uses
> the same command line option parser. So you can pass in the args when
> running your runner file. Like so:
>
> ruby story.rb -f=html
> or the verbose way:
> ruby story.rb --format=html
Man, you gentleme
Yes, that was it. Thanks
Ed
On Mon, Jun 2, 2008 at 1:10 PM, Pat Maddox <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 2, 2008 at 11:06 AM, Ed Howland <[EMAIL PROTECTED]> wrote:
>> HI,
>>
>> After I upgraded to RSpec 1.1.4 (from git), my stories all failed. I
>> was using Webrat and the first thing I no
On Mon, Jun 2, 2008 at 11:38 AM, Rick DeNatale <[EMAIL PROTECTED]> wrote:
> A colleague just came in and asked me about a problem he was having with
> stub_render, which reminded me of another issue he had a week or so ago,
> which seems related.
>
> Let me start with the earlier issue.
>
> He was
David Chelimsky wrote:
On Jun 2, 2008, at 11:28 AM, Matt Wynne wrote:
Hi all,
I'm just getting to grips with rspec, and I'm trying to put together a
showy demo. We're trying to use the (plain text) stories feature, rather
than the specs. I'd like to show off a fancy HTML report of the results
On Jun 2, 2008, at 11:28 AM, Matt Wynne wrote:
Hi all,
I'm just getting to grips with rspec, and I'm trying to put together a
showy demo. We're trying to use the (plain text) stories feature,
rather
than the specs. I'd like to show off a fancy HTML report of the
results
if possible.
So it
Matt Wynne wrote:
Hi all,
I'm just getting to grips with rspec, and I'm trying to put together a
showy demo. We're trying to use the (plain text) stories feature, rather
than the specs. I'd like to show off a fancy HTML report of the results
if possible.
So it seems I can do this from the spec
A colleague just came in and asked me about a problem he was having with
stub_render, which reminded me of another issue he had a week or so ago,
which seems related.
Let me start with the earlier issue.
He was trying to write specs for a method which sends the same message
possibly multiple time
Hi all,
I'm just getting to grips with rspec, and I'm trying to put together a
showy demo. We're trying to use the (plain text) stories feature, rather
than the specs. I'd like to show off a fancy HTML report of the results
if possible.
So it seems I can do this from the spec command line tool, b
On Mon, Jun 2, 2008 at 11:06 AM, Ed Howland <[EMAIL PROTECTED]> wrote:
> HI,
>
> After I upgraded to RSpec 1.1.4 (from git), my stories all failed. I
> was using Webrat and the first thing I noticed was the 'visits' method
> was gone. I then backtracked to just using 'get' and got the same
> undefi
HI,
After I upgraded to RSpec 1.1.4 (from git), my stories all failed. I
was using Webrat and the first thing I noticed was the 'visits' method
was gone. I then backtracked to just using 'get' and got the same
undefined method exception. I confirmed it was still working in 1.1.3
Eventually, I got
On Sun, Jun 1, 2008 at 1:55 PM, David Chelimsky <[EMAIL PROTECTED]> wrote:
> On Jun 1, 2008, at 12:17 PM, Matthias Hennemeyer wrote:
>
>> Hey!
>>
>> I have implemented a quick solution for the should != .. , should !~ ...
>> 'problem'.
>> It uses source code inspection (I think it's the only way) a
On Sun, Jun 1, 2008 at 10:13 PM, Scott Taylor <[EMAIL PROTECTED]>
wrote:
>
> On Jun 1, 2008, at 4:55 PM, David Chelimsky wrote:
>
>>
>> RSpec is already getting dinged for being slower than test/unit. Making it
>> run any slower than it already does is a deal breaker for me.
>>
>
> It seems perfec
>
> Message: 2
> Date: Thu, 29 May 2008 06:35:01 -0700
> From: David Chelimsky <[EMAIL PROTECTED]>
> Subject: Re: [rspec-users] Coloured output in rspec 1.1.4
> To: rspec-users@rubyforge.org
> Message-ID: <[EMAIL PROTECTED]>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
On 2 Jun 2008, at 04:29, T K wrote:
I just noticed that `rake notes` in rails 2.0.2 doesn't check `spec`
directory. So, what I annotated with "FIXME", "TODO" and "OPTIMIZE" on
*_spec.rb are discarded.
Is there any quick way to `rake notes` task to check `spec` directory?
You could redefine t
28 matches
Mail list logo
