running spec - Empty test suite
Anyone else seeing this on #500? When I run an individual specI get this:
/opt/local/bin/ruby -e STDOUT.sync=true;STDERR.sync=true;load($0=ARGV.shift) /opt/local/bin/rdebug-ide --port 51278 -- /Users/nick/code/src/clients/zumio/reach-out-global/script/spec --require teamcity/spec/runner/formatter/teamcity/formatter --format Spec::Runner::Formatter::TeamcityFormatter:matrix /Users/nick/code/src/clients/zumio/reach-out-global/spec/mixins/trashable_spec.rb
Fast Debugger (ruby-debug-ide 0.4.0) listens on :51278
Empty test suite.
Please sign in to leave a comment.
Nicholas,
Do you mean that your trashable_spec.rb contains spec examples, but RubyMine finds nothing?
Yes.
And what will happen if you
1. Run in RubyMine but not in debug mode?
2. Run in debug mode but without ruby interpreter argument: -e STDOUT.sync=true;STDERR.sync=true;load($0=ARGV.shift)
3. Run spec example from console?
Also does process output(in console window) contains any other information except these 3 lines?
1. Same thing as if I run it in debug.
2. Same thing as above, except much faster in reporting an empty test suite.
3. It works.
Cheers,
Nicholas
----
Ah, I see the problem now. I somehow gained the habit of running specs in debug mode. Running it normally produces output:
This is a local issue - we moved from using rspec as a plugin to a gem. The install script for the rspec plugin created some files in the scripts directory which werent removed.
Nicholas F,
As far as I understand you solved that problem and all works ok ?
Hi,
I havent managed to solve the problem yet, though I haven't had the time to look at it. For some reason rubymine can't find a live_fixtures.rb file which is required by spec_helper (and which is in the same directory as spec_helper). I suppose it must have to do with the load path of rubymine when it's asked to run a spec on the fly (without any configuration), but it should *just work*, I think.
Thanks for keeping an eye on it. I might be slow to respond, but I'll get back to it.
Something else I've noticed, very occasionally, is that rubymine can be slow, sometimes, with larger ruby files. I've seen the problem happen twice on a module file, though the size is only moderate (a few screens worth).