[rspec-devel] [ rspec-Feature Requests-10010 ] Number executed specs; support --spec-number switch

[noreply at rubyforge.org]

Feature Requests item #10010, was opened at 2007-04-10 11:55
You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=3152&aid=10010&group_id=797

Category: runner / command line
Group: None
>Status: Deleted
Priority: 3
Submitted By: Chris Hoffman (hoffman_c)
Assigned to: Nobody (None)
Summary: Number executed specs; support --spec-number switch

Initial Comment:
I am not sure if this is at all possible, but I have been thinking about ticket #9287, and it seems like the following might be an easier way to go.  If you number all of the specs that are being executed for a particular command, then the user can see which number failed, fix the problem, and run that specific spec again.

----------------------------------------------------------------------

>Comment By: Chris Hoffman (hoffman_c)
Date: 2007-04-10 12:14

Message:
Yeah, I was totally thinking of the solution without
thinking about the actual use case.  Good catch.

----------------------------------------------------------------------

Comment By: David Chelimsky (dchelimsky)
Date: 2007-04-10 12:07

Message:
I believe your goal is to only run the specs that have just failed until you get them to pass, yes?

If so, you can do that now (in 0.9) using the following in spec.opts:

--failures
previous_spec_failures.txt
--example
previous_spec_failures.txt

now either do this:

spec spec -O spec/spec.opts

or

rake spec (assuming the rake task is set up to read the opts file, which it is now by default)

----------------------------------------------------------------------

You can respond by visiting: 
http://rubyforge.org/tracker/?func=detail&atid=3152&aid=10010&group_id=797