TeamCity Rake Runner Plugin isn't compatible with this RSpec version.
Hello, I have found similar threads from the past, but all of them are quite old and that's why I am starting this one.
I have RubyMine 6.3.3, Rails 4.1.1 and Rspec 3.0.2 and Capybara 2.4.1.
My spec-test suite runs fine from command line with 1 expected failed item:
$ rspec
F.
Failures:
1) the signin process signs me in
Failure/Error: expect(page).to have_content 'successsful'
expected #has_content?("successsful") to return true, got false
# ./spec/model/user_login_spec.rb:13:in `block (2 levels) in <top (required)>'
Finished in 0.45149 seconds (files took 2.12 seconds to load)
2 examples, 1 failure
Failed examples:
rspec ./spec/model/user_login_spec.rb:6 # the signin process signs me in
but the same specs started from RubyMine tells:
/Users/jan/.rvm/rubies/ruby-2.0.0-p451/bin/ruby -e $stdout.sync=true;$stderr.sync=true;load($0=ARGV.shift) /Users/jan/Development/Ruby/repo/FindElephant2/bin/spring rspec /Users/jan/Development/Ruby/repo/FindElephant2/spec --require teamcity/spec/runner/formatter/teamcity/formatter --format Spec::Runner::Formatter::TeamcityFormatter --pattern **/*_spec.rb --backtrace
Testing started at 00:02 ...
2 examples, 2 failures, 0 passed
Finished in 0.54492 seconds
TeamCity Rake Runner Plugin isn't compatible with this RSpec version.
Following examples weren't finished:
1. Example : 'the signin process signs me in'
/Applications/RubyMine.app/rb/testing/patch/bdd/teamcity/spec/runner/formatter/teamcity/rspec3_formatter.rb:261:in `dump_summary': TeamCity Rake Runner Plugin isn't compatible with this RSpec version. (Rake::TeamCity::InnerException)
Following examples weren't finished:
1. Example : 'the signin process signs me in'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/rspec-core-3.0.2/lib/rspec/core/reporter.rb:137:in `block in notify'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/rspec-core-3.0.2/lib/rspec/core/reporter.rb:136:in `each'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/rspec-core-3.0.2/lib/rspec/core/reporter.rb:136:in `notify'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/rspec-core-3.0.2/lib/rspec/core/reporter.rb:118:in `finish'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/rspec-core-3.0.2/lib/rspec/core/reporter.rb:56:in `ensure in report'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/rspec-core-3.0.2/lib/rspec/core/reporter.rb:56:in `report'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/rspec-core-3.0.2/lib/rspec/core/runner.rb:108:in `run_specs'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/rspec-core-3.0.2/lib/rspec/core/runner.rb:86:in `run'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/rspec-core-3.0.2/lib/rspec/core/runner.rb:70:in `run'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/rspec-core-3.0.2/lib/rspec/core/runner.rb:38:in `invoke'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/rspec-core-3.0.2/exe/rspec:4:in `<top (required)>'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/activesupport-4.1.1/lib/active_support/dependencies.rb:241:in `load'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/activesupport-4.1.1/lib/active_support/dependencies.rb:241:in `block in load'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/activesupport-4.1.1/lib/active_support/dependencies.rb:232:in `load_dependency'
from /Users/jan/.rvm/gems/ruby-2.0.0-p451@rails41/gems/activesupport-4.1.1/lib/active_support/dependencies.rb:241:in `load'
from /Users/jan/.rvm/rubies/ruby-2.0.0-p451/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from /Users/jan/.rvm/rubies/ruby-2.0.0-p451/lib/ruby/site_ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
from -e:1:in `<main>'
Process finished with exit code 1
Interesting is (at least for me) that when I write not failing specs then even in RubyMine tests run fine with expected green result.
Do I need to use an older rspec gem?
Regards,
Jan
Please sign in to leave a comment.
Hi Jan,
the mesasge a little bit cryptic but it actually means that we missed notification about finishing several tests and it looks like a but in our formatter.
Could you please file a bug in our tracker (http://youtrack.jetbrains.com/issues/RUBY) with test project attached.
Thanks in advance, Oleg.
I have this same problem. I am using OptParser within the class I am testing (to test arguments that I pass in).
I wonder if the OP is also using OptParse.
Since RSpec uses OptParse to handle it's arguments, I wonder if this is part of the problem? (using OptParse in the class under test)
Hello Ashley,
it's quite difficult to say what's causing the problem without seeing the code itself. Would it be possible to provide a project for reproduce? (you can write me at rubymine-support@jetbrains.com)
FWIW: I just ran into this problem. For me it turned out to be an exception that was being raised in an RSpec after(:all) block. Fixing what caused the exception was the solution. I had to run rspec from the command line to see the error properly.
Similarly, I had this happen with an error (which was masked) in a custom RSpec reporter. I found it by running the test in the debugger, with a breakpoint on the rspec/core/reporter.rb line given by the TeamCity error message stacktrace.