Cucumber Tests - Can run but can't debug...
Hi All,
Does anyone know why I can RUN a feature file (from context menu or configuration tab) but when I DEBUG it I get "no tests were found" (RM: 2.0.2)
I have the following gems attached to the project.
ruby-debug 0.10.3
ruby-debug-base 0.10.3
ruby-debug-ide 0.4.9
Any thoughts? I'm going a little nuts...
Many Thanks. I LOVE RubyMine.
Tim
(Console)
Works:
/usr/bin/ruby -e STDOUT.sync=true;STDERR.sync=true;load($0=ARGV.shift) /usr/bin/cucumber /Users/twalker/Development/smartgrid/apollo/features/api/thermostat_setting.feature --format Teamcity::Cucumber::Formatter --expand --backtrace --verbose --color
(Results)
Does not work:
Does not work:
/usr/bin/ruby -r /Applications/RubyMine 2.0.2.app/rb/gems/rdebug-hack.rb -e STDOUT.sync=true;STDERR.sync=true;load($0=ARGV.shift) /usr/bin/rdebug-ide --port 59858 -- /usr/bin/cucumber /Users/twalker/Development/smartgrid/apollo/features/api/thermostat_setting.feature --format Teamcity::Cucumber::Formatter --expand --backtrace --verbose --color
Testing started at 11:15 AM ...
Fast Debugger (ruby-debug-ide 0.4.9) listens on :59858
Process finished with exit code 1
Empty test suite.
Testing started at 11:15 AM ...
Fast Debugger (ruby-debug-ide 0.4.9) listens on :59858
Process finished with exit code 1
Empty test suite.
请先登录再写评论。
While I do not understand this yet it appears that, if you add an Exception breakpoint (Exception or StandardError) you will not be able to debug cucumber features. I had an API test that was expecting a response of 200 but was getting a 500 so I thought I could simply break on that exceptions. This is when I stopped being able to debug Cucumber. Any thoughts?
Thanks again for an amazing product.
Sincerely,
Tim