-
Notifications
You must be signed in to change notification settings - Fork 88
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
Always reports 0 tests #97
Comments
Hi, the tests seem to actually run well the first time and then there's another run without any tests run... Have you tried to run the actual command run by guard-minitest? bundle exec ruby -I"test" -I"spec" -r bundler/setup -r minitest/autorun -r ./test/unit/some_test.rb -r /home/dbonev/.rbenv/versions/2.0.0-p247/lib/ruby/gems/2.0.0/gems/guard-minitest-2.1.3/lib/guard/minitest/runners/old_runner.rb -e "" |
I see a similar thing as mentioned in #114 (comment) |
I'm seeing this error too. Whenever I change a file in is there a way to only notify when tests are actually run?
EDIT: oops: nevermind, i see the error. i commented out one |
I had the same issue until I specified the |
With guard:
Without guard:
I have removed minitest-reporters from Gemfile to eliminate it as a reason.
Guardfile:
The text was updated successfully, but these errors were encountered: