I'm sure this has been covered before, but after some time all I've been able
to find on the intarwebs are references to the use of code coverage tests to
identify code that is not used by any current tests.
I guess the assumption is that you've specced your application completely, and
any code
On Thu, Feb 11, 2010 at 12:13 AM, Mike Sassak wrote:
> On Wed, Feb 10, 2010 at 10:17 PM, Phillip Koebbe
> wrote:
>> When I do
>>
>> script/spec -c -f n spec/models/**/*_spec.rb
>>
>> I get
>>
>> /Library/Ruby/Gems/1.8/gems/rspec-1.3.0/lib/spec/runner/options.rb:283:in
>> `files_to_load': File or
On Wed, Feb 10, 2010 at 10:17 PM, Phillip Koebbe
wrote:
> When I do
>
> script/spec -c -f n spec/models/**/*_spec.rb
>
> I get
>
> /Library/Ruby/Gems/1.8/gems/rspec-1.3.0/lib/spec/runner/options.rb:283:in
> `files_to_load': File or directory not found: spec/models/**/*_spec.rb
> (RuntimeError)
>
When I do
script/spec -c -f n spec/models/**/*_spec.rb
I get
/Library/Ruby/Gems/1.8/gems/rspec-1.3.0/lib/spec/runner/options.rb:283:in `files_to_load':
File or directory not found: spec/models/**/*_spec.rb (RuntimeError)
Yet, if I go into irb and do
Dir.glob('spec/models/**/*_spec.rb')
I
David Chelimsky wrote:
> # purely hypothetical code - do not try this at home
> Rspec::Core.configure do |c|
> c.after(:each) do
> if running_example.metadata[:status] == 'failed'
> running_example.example_group.break
> end
> end
> end
>
> Coming soon, but not quite yet.
Very co
