rspec users - Sep 2007 - "rake spec:doc" returns NO NAME (due to --dry-run) for each specify block

I went ahead and moved to the trunk versions of RSpec and Spec:Rails because
I wanted to try out the new Story Runner feature. However, when I tried to
do "rake spec:doc", I got the following:

AccountController
- NO NAME (Because of --dry-run)

AccountHelper
- NO NAME (Because of --dry-run)

User (in general)
- NO NAME (Because of --dry-run)
- NO NAME (Because of --dry-run)
- NO NAME (Because of --dry-run)
- NO NAME (Because of --dry-run)
- NO NAME (Because of --dry-run)
- NO NAME (Because of --dry-run)

I emptied everything out of my spec.opts file just to make sure it
wasn''t
some setting there causing problems, but that still had no effect. I
haven''t
submitted this as a bug yet because I''m still holding out the
possibility
that I''m simply doing something wrong.

Thanks,

Chris Pratt
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/rspec-users/attachments/20070916/dee445a0/attachment.html

When you use spec:doc, it does a dry-run, in which case the blocks are
never executed, in which case you get this message for every block
relying on auto-generated names:

describe 5 do
  it { 5.should == 5}
end

If you mean to use the specdoc format (i.e. it really runs everything
and you get the output from all the strings passed to describe and
it), do this:

rake spec --format specdoc

or

rake spec -fs

Cheers,
David


On 9/16/07, Christopher D. Pratt <chrisdpratt at gmail.com>
wrote:
> I went ahead and moved to the trunk versions of RSpec and Spec:Rails
because
> I wanted to try out the new Story Runner feature. However, when I tried to
> do "rake spec:doc", I got the following:
>
> AccountController
> - NO NAME (Because of --dry-run)
>
> AccountHelper
> - NO NAME (Because of --dry-run)
>
> User (in general)
> - NO NAME (Because of --dry-run)
> - NO NAME (Because of --dry-run)
> - NO NAME (Because of --dry-run)
> - NO NAME (Because of --dry-run)
> - NO NAME (Because of --dry-run)
> - NO NAME (Because of --dry-run)
>
> I emptied everything out of my spec.opts file just to make sure it
wasn''t
> some setting there causing problems, but that still had no effect. I
haven''t
> submitted this as a bug yet because I''m still holding out the
possibility
> that I''m simply doing something wrong.
>
> Thanks,
>
> Chris Pratt
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

This happens if you have it blocks with no name. RSpec tries to
generate names based on the code inside, but with dry run it isn''t
executed, so it can''t.

But maybe you don''t have empty it blocks? I''m just guessing
here...

Aslak

On 9/16/07, Christopher D. Pratt <chrisdpratt at gmail.com>
wrote:
> I went ahead and moved to the trunk versions of RSpec and Spec:Rails
because
> I wanted to try out the new Story Runner feature. However, when I tried to
> do "rake spec:doc", I got the following:
>
> AccountController
> - NO NAME (Because of --dry-run)
>
> AccountHelper
> - NO NAME (Because of --dry-run)
>
> User (in general)
> - NO NAME (Because of --dry-run)
> - NO NAME (Because of --dry-run)
> - NO NAME (Because of --dry-run)
> - NO NAME (Because of --dry-run)
> - NO NAME (Because of --dry-run)
> - NO NAME (Because of --dry-run)
>
> I emptied everything out of my spec.opts file just to make sure it
wasn''t
> some setting there causing problems, but that still had no effect. I
haven''t
> submitted this as a bug yet because I''m still holding out the
possibility
> that I''m simply doing something wrong.
>
> Thanks,
>
> Chris Pratt
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

Thanks for all the responses. Unfortunately, I apparently just like being
difficult.

Tom: I installed the new version of rspec on a fresh app, so the first run
of  script/generate rspec was from the trunk version ... good idea though,
because it sounds like something I would have done

-----

David: all of my specify blocks have the string names on them, so that
doesn''t seem like the problem. I also tried running the two commands
you
provided but both returned the following errors:

$ rake spec --format specdoc
rake aborted!
No Rakefile found (looking for: ormat)
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1934:in
`raw_load_rakefile''
(See full trace by running task with --trace)

$ rake spec -fs
rake aborted!
No Rakefile found (looking for: s)
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1934:in
`raw_load_rakefile''
(See full trace by running task with --trace)

Is there some way I can turn off dry run for spec:doc?

--------

Aslak: I''m not relying on auto-generated names. Although I definitely
agree
that spec:doc is acting as if I were

-------

Any other ideas? ;)

Thanks,

Chris Pratt



On 9/16/07, aslak hellesoy <aslak.hellesoy at gmail.com>
wrote:
>
> This happens if you have it blocks with no name. RSpec tries to
> generate names based on the code inside, but with dry run it isn''t
> executed, so it can''t.
>
> But maybe you don''t have empty it blocks? I''m just
guessing here...
>
> Aslak
>
> On 9/16/07, Christopher D. Pratt <chrisdpratt at gmail.com> wrote:
> > I went ahead and moved to the trunk versions of RSpec and Spec:Rails
> because
> > I wanted to try out the new Story Runner feature. However, when I
tried
> to
> > do "rake spec:doc", I got the following:
> >
> > AccountController
> > - NO NAME (Because of --dry-run)
> >
> > AccountHelper
> > - NO NAME (Because of --dry-run)
> >
> > User (in general)
> > - NO NAME (Because of --dry-run)
> > - NO NAME (Because of --dry-run)
> > - NO NAME (Because of --dry-run)
> > - NO NAME (Because of --dry-run)
> > - NO NAME (Because of --dry-run)
> > - NO NAME (Because of --dry-run)
> >
> > I emptied everything out of my spec.opts file just to make sure it
> wasn''t
> > some setting there causing problems, but that still had no effect. I
> haven''t
> > submitted this as a bug yet because I''m still holding out the
> possibility
> > that I''m simply doing something wrong.
> >
> > Thanks,
> >
> > Chris Pratt
> >
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
> >
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/rspec-users/attachments/20070916/4a13d302/attachment.html

On 9/17/07, Christopher D. Pratt <chrisdpratt at gmail.com>
wrote:
> Thanks for all the responses. Unfortunately, I apparently just like being
> difficult.
>
> Tom: I installed the new version of rspec on a fresh app, so the first run
> of  script/generate rspec was from the trunk version ... good idea though,
> because it sounds like something I would have done
>
> -----
>
> David: all of my specify blocks have the string names on them, so that
> doesn''t seem like the problem. I also tried running the two
commands you
> provided but both returned the following errors:
>
> $ rake spec --format specdoc
> rake aborted!
> No Rakefile found (looking for: ormat)
> /usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1934:in
> `raw_load_rakefile''
> (See full trace by running task with --trace)
>
> $ rake spec -fs
> rake aborted!
> No Rakefile found (looking for: s)
> /usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1934:in
> `raw_load_rakefile''
> (See full trace by running task with --trace)
>
>  Is there some way I can turn off dry run for spec:doc?
>
> --------
>
> Aslak: I''m not relying on auto-generated names. Although I
definitely agree
> that spec:doc is acting as if I were
>
> -------
>
> Any other ideas? ;)
>
Help us reproduce what you see
> Thanks,
>
> Chris Pratt
>
>
>
>
> On 9/16/07, aslak hellesoy <aslak.hellesoy at gmail.com> wrote:
> > This happens if you have it blocks with no name. RSpec tries to
> > generate names based on the code inside, but with dry run it
isn''t
> > executed, so it can''t.
> >
> > But maybe you don''t have empty it blocks? I''m just
guessing here...
> >
> > Aslak
> >
> > On 9/16/07, Christopher D. Pratt <chrisdpratt at gmail.com >
wrote:
> > > I went ahead and moved to the trunk versions of RSpec and
Spec:Rails
> because
> > > I wanted to try out the new Story Runner feature. However, when I
tried
> to
> > > do "rake spec:doc", I got the following:
> > >
> > > AccountController
> > > - NO NAME (Because of --dry-run)
> > >
> > > AccountHelper
> > > - NO NAME (Because of --dry-run)
> > >
> > > User (in general)
> > > - NO NAME (Because of --dry-run)
> > > - NO NAME (Because of --dry-run)
> > > - NO NAME (Because of --dry-run)
> > > - NO NAME (Because of --dry-run)
> > > - NO NAME (Because of --dry-run)
> > > - NO NAME (Because of --dry-run)
> > >
> > > I emptied everything out of my spec.opts file just to make sure
it
> wasn''t
> > > some setting there causing problems, but that still had no
effect. I
> haven''t
> > > submitted this as a bug yet because I''m still holding
out the
> possibility
> > > that I''m simply doing something wrong.
> > >
> > > Thanks,
> > >
> > > Chris Pratt
> > >
> > > _______________________________________________
> > > rspec-users mailing list
> > > rspec-users at rubyforge.org
> > > http://rubyforge.org/mailman/listinfo/rspec-users
> > >
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
> >
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

On 9/17/07, Christopher D. Pratt <chrisdpratt at gmail.com>
wrote:
> Thanks for all the responses. Unfortunately, I apparently just like being
> difficult.
>
> Tom: I installed the new version of rspec on a fresh app, so the first run
> of  script/generate rspec was from the trunk version ... good idea though,
> because it sounds like something I would have done
>
> -----
>
> David: all of my specify blocks have the string names on them, so that
> doesn''t seem like the problem. I also tried running the two
commands you
> provided but both returned the following errors:
>
> $ rake spec --format specdoc
> rake aborted!
> No Rakefile found (looking for: ormat)
> /usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1934:in
> `raw_load_rakefile''
> (See full trace by running task with --trace)
>
> $ rake spec -fs
> rake aborted!
> No Rakefile found (looking for: s)
> /usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1934:in
> `raw_load_rakefile''
> (See full trace by running task with --trace)
Sorry - wrong commands. Try this (assumes a rails app):

script/spec spec -fs
>  Is there some way I can turn off dry run for spec:doc?
spec:doc == dry run

So probably not :)

Cheers,
David
>
> --------
>
> Aslak: I''m not relying on auto-generated names. Although I
definitely agree
> that spec:doc is acting as if I were
>
> -------
>
> Any other ideas? ;)
>
> Thanks,
>
> Chris Pratt
>
>
>
>
> On 9/16/07, aslak hellesoy <aslak.hellesoy at gmail.com> wrote:
> > This happens if you have it blocks with no name. RSpec tries to
> > generate names based on the code inside, but with dry run it
isn''t
> > executed, so it can''t.
> >
> > But maybe you don''t have empty it blocks? I''m just
guessing here...
> >
> > Aslak
> >
> > On 9/16/07, Christopher D. Pratt <chrisdpratt at gmail.com >
wrote:
> > > I went ahead and moved to the trunk versions of RSpec and
Spec:Rails
> because
> > > I wanted to try out the new Story Runner feature. However, when I
tried
> to
> > > do "rake spec:doc", I got the following:
> > >
> > > AccountController
> > > - NO NAME (Because of --dry-run)
> > >
> > > AccountHelper
> > > - NO NAME (Because of --dry-run)
> > >
> > > User (in general)
> > > - NO NAME (Because of --dry-run)
> > > - NO NAME (Because of --dry-run)
> > > - NO NAME (Because of --dry-run)
> > > - NO NAME (Because of --dry-run)
> > > - NO NAME (Because of --dry-run)
> > > - NO NAME (Because of --dry-run)
> > >
> > > I emptied everything out of my spec.opts file just to make sure
it
> wasn''t
> > > some setting there causing problems, but that still had no
effect. I
> haven''t
> > > submitted this as a bug yet because I''m still holding
out the
> possibility
> > > that I''m simply doing something wrong.
> > >
> > > Thanks,
> > >
> > > Chris Pratt
> > >
> > > _______________________________________________
> > > rspec-users mailing list
> > > rspec-users at rubyforge.org
> > > http://rubyforge.org/mailman/listinfo/rspec-users
> > >
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
> >
>
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>