Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

autotest stops running tests after the last failing test succeeds #63

Closed
shalonwood opened this issue Aug 15, 2014 · 4 comments
Closed
Assignees

Comments

@shalonwood
Copy link

When I fix the last failing test in my test suite, autotest stops running tests. It looks like it can't map the files to tests anymore. The last bit of the output when running it with -v is:

{"test/controllers/keys_controller_test.rb"=>2014-08-15 12:09:13 -0400}
/usr/bin/ruby1.9.1 -I.:lib:test -rubygems -e "gem 'minitest'; %w[minitest/autorun test/controllers/keys_controller_test.rb].each { |f| require f }"
Run options: --seed 22324

# Running:



Finished in 0.000738s, 0.0000 runs/s, 0.0000 assertions/s.

0 runs, 0 assertions, 0 failures, 0 errors, 0 skips
{"test/controllers/keys_controller_test.rb"=>2014-08-15 12:09:13 -0400}
/usr/bin/ruby1.9.1 -I.:lib:test -rubygems -e "gem 'minitest'; %w[minitest/autorun test/controllers/keys_controller_test.rb].each { |f| require f }"
Run options: --seed 17636

# Running:

E.

Finished in 0.491539s, 4.0688 runs/s, 16.2754 assertions/s.

  1) Error:
KeysControllerTest#test_Should_not_return_expired_keys_for_the_requested_user_and_host:
NoMethodError: undefined method `created_at' for nil:NilClass
    test/controllers/keys_controller_test.rb:79:in `block in <class:KeysControllerTest>'

2 runs, 8 assertions, 0 failures, 1 errors, 0 skips
{"test/controllers/keys_controller_test.rb"=>2014-08-15 12:09:26 -0400}
/usr/bin/ruby1.9.1 -I.:lib:test -rubygems test/controllers/keys_controller_test.rb -n "/^(test_Should_not_return_expired_keys_for_the_requested_user_and_host)$/"
{"test/controllers/keys_controller_test.rb"=>2014-08-15 12:09:26 -0400}
/usr/bin/ruby1.9.1 -I.:lib:test -rubygems test/controllers/keys_controller_test.rb -n "/^(test_Should_not_return_expired_keys_for_the_requested_user_and_host)$/"
Run options: -n "/^(test_Should_not_return_expired_keys_for_the_requested_user_and_host)$/" --seed 36913

# Running:

.

Finished in 0.385816s, 2.5919 runs/s, 15.5515 assertions/s.

1 runs, 6 assertions, 0 failures, 0 errors, 0 skips
{"test/controllers/keys_controller_test.rb"=>2014-08-15 12:09:26 -0400}
No tests matched test/controllers/keys_controller_test.rb
@zenspider
Copy link
Member

Sorry it's taken me so long to get back to you. This came in while I was travelling.

Are you using the autotest-rails plugin gem?

@zenspider zenspider self-assigned this Aug 20, 2014
@zenspider
Copy link
Member

anything?

@shalonwood
Copy link
Author

Whoops, sorry! I thought I'd responded to this last week. It looks like the error may have been related to the autotest-inotify plugin; just before you posted that question I accidentally blew my .autotest away, and when I recreated it I didn't remember to add that back in. Shortly afterwards, I noticed that the problem wasn't happening any longer. A bit of testing seemed to imply that it was a result of that plugin.

I didn't have time to do much testing, so it could have been coincidence, however. Also, to answer your question, yes, I'm using autotest-rails.

@zenspider
Copy link
Member

Can you file a bug against autotest-inotify and point them back to here?

Closing this ticket.

@seattlerb seattlerb locked and limited conversation to collaborators Jan 24, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants