On Tue, Oct 28, 2008 at 12:31 PM, Lenny Marks <lenny at aps.org>
wrote:
> Ooops. I meant the -l option not -n.
>
> It seems that '-l' command line option for rspec stopped working
as of
> rspec 1.1.3.
It's been working for me. I wrote a Vim script that runs the current
spec
(in whatever window it might be) with DRb, so it takes about a
second. It's
made a big difference in my TDD/BDD work cycle.
///ark
Sorry for not replying to the thread but I'm not getting any mail from
rspec-users right now for whatever reason.
It looks like it is an issue specific to jruby.
With rspec-1.1.11 and jruby-1.4
#linenumber_spec.rb
describe "line number" do
it "should be example one" do
true.should be_true
end
it "should be another example" do
true.should be_true
end
end
> jruby-1.1.4/bin/jruby $GEM_HOME/bin/spec -l 2 $HOME/tmp/
linenumber_spec.rb
Finished in 0.013457 seconds
0 examples, 0 failures
> ruby $GEM_HOME/bin/spec -l 2 $HOME/tmp/linenumber_spec.rb
.
Finished in 0.006864 seconds
1 example, 0 failures
-lenny
_______________________________________________
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
