Skip to content

Incompatible with simplecov: does not find a rspec.failures file  #4

Description

@jmuheim

I have installed rspec-rerun as told by the README, but it doesn't seem to work.

I've run rake which runs all tests, and they all passed. But then it seems to hang itself, only a Ctrl-C brings me back to the console. Take a look at the output, it seems to have problems finding an rspec.failures file. This should be generated automatically, right?

# ...
# some more rspec output before this...

Pending:
  TimeRecord#duration passing a string as started_at/finished_at invalid date string does not accept it
    # Not working with MongoDB/Mongoid/validates_timeliness 3 yet
    # ./spec/models/time_record_spec.rb:106
  Vertical Menu links to calendar
    # Kalender ist zur Zeit nicht aktiv
    # ./spec/requests/menu/vertical_menu_spec.rb:34
  TimeRecordManagement#edit doesn't edit a time record when dates are wrong
    # Not working with MongoDB/Mongoid/validates_timeliness 3 yet
    # ./spec/requests/users/manage_own_timerecords_spec.rb:79

Finished in 3 minutes 54.27 seconds
880 examples, 0 failures, 3 pending
Coverage report generated for RSpec to /Users/josh/Documents/Work/Sientia/iq/coverage. 2195 / 2368 LOC (92.69%) covered.
Rack::File headers parameter replaces cache_control after Rack 1.5.
^C
Exiting... Interrupt again to exit immediately.
^C
Exiting... Interrupt again to exit immediately.
Coverage report generated for RSpec to /Users/josh/Documents/Work/Sientia/iq/coverage. 1716 / 2215 LOC (77.47%) covered.
rake aborted!
No such file or directory - rspec.failures
/Users/josh/.rvm/gems/ruby-1.9.3-p327@iq/gems/rspec-rerun-0.1.1/lib/tasks/rspec.rake:31:in `read'
/Users/josh/.rvm/gems/ruby-1.9.3-p327@iq/gems/rspec-rerun-0.1.1/lib/tasks/rspec.rake:31:in `block in <top (required)>'
/Users/josh/.rvm/gems/ruby-1.9.3-p327@global/bin/ruby_noexec_wrapper:14:in `eval'
/Users/josh/.rvm/gems/ruby-1.9.3-p327@global/bin/ruby_noexec_wrapper:14:in `<main>'
Tasks: TOP => default => rspec-rerun:spec
(See full trace by running task with --trace)

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions