When I try to run the tests from within RubyMine I have an issue. But what is strange is that it work fine when I run the tests from the command line.
"Test framework quit unexpectedly"
/usr/local/rvm/rubies/ruby-1.9.3-p392/bin/ruby -e $stdout.sync=true;$stderr.sync=true;load($0=ARGV.shift) -Itest /Users/sabour/Desktop/EIP/project/test/controllers/categories_controller_test.rb
Testing started at 1:39 AM ...
Run options: --seed 14336
# Running tests:
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228: warning: nested repeat operator + and ? was replaced with '*'
...
Finished tests in 2.554592s, 1.1744 tests/s, 8.6119 assertions/s.
3 tests, 22 assertions, 0 failures, 0 errors, 0 skips
Process finished with exit code 0
Maybe the problem come from that line ?
/usr/local/rvm/gems/ruby-1.9.3-p392/gems/activesupport-4.0.0/lib/active_support/dependencies.rb:228: warning: nested repeat operator + and ? was replaced with '*' ...
Mode: Test script Use pre-load server: none Ruby arguments: -e $stdout.sync=true;$stderr.sync=true;load($0=ARGV.shift) -Itest Ruby SDK: project
But I would love to have something like this:
Thank you
You should be sure that your test suite is running with
RAILS_ENV=test
For RubyMine you can set this up in
Run > Edit Configurations.. > Choose test suite you want to run (i.e. spec: project_name) > Environment variables
and there add variable mentioned above.There is a nice tutorial for setting up RubyMine tests in their online help, which helped me resolve the same problem as you describe (for
Test::Unit
-style tests). Basically you need to include theminitest
andminitest-reporters
gems into your project and add a call to use the new format of tests reporting:Take a look at the tutorial for more options.
I had the same problem when running from RubyMine (but not from command line). It was fixed by restarting spring:
You can fix it specifying the PATH for RSpec. To find the right path in Ubuntu, I used the command
In RubyMine, go to menu "Run" > "Edit Configurations", mark "Use custom RSpec runner script", and set the path found previously.
You can get this error when some of the gems are not checked out, so you will need to run
bundle install
. Run your test from terminal and you will get an error if that is your caseI had the same problem, and it was caused by not installing (globally?) the ruby gems of the testing library. For instance, for the minitest testing framework (you didn't specify which one you use), just run from command line:
This solved the problem to me.