blocks|key|737148|text|您可以在项目的根目录中创建一个.rspec配置文件，并包含以下行：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|737149|--debug|code-block|syntax|javascript|737150|entityMap^0|F|6|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

You can create an <code>.rspec</code> configuration file in the root of your project and include the line:

<pre><code>--debug
</code></pre>

blocks|key|737215|text|我发现在rSpec中调试的最好方法是在'spec_helper.rb‘文件中添加以下代码|type|unstyled|depth|inlineStyleRanges|entityRanges|data|737216|def+logger
++Rails.logger
end|code-block|syntax|javascript|737217|然后，您可以访问rSpec文件中的所有记录器方法，并合并标记日志之类的内容。当然，这是针对Rails+3和更高版本的。如果您在Rails+3之前有任何内容，请添加以下内容：|737218|def+logger
++RAILS_DEFAULT_LOGGER
end|737219|一旦准备好了日志语句，就可以输入|737220|tail+-f+log/test.log|737221|在终端shell中，以便在测试运行时监视日志记录语句。|737222|当然，在实际的rspec测试中，您需要输入如下内容|737223|logger.debug+"#{1.class}"++#+=>+Fixnum|737224|如果您想从测试日志的其余部分中过滤调试语句，只需在调试语句前面添加一个随机字符串，并将tail命令的输出通过管道传递给grep。|737225|示例：|737226|logger.debug+"random_string+#{1.class}"+++#+=>+Fixnum

tail+-f+log/test.log+%7C+grep+random_string|737227|更新|737228|我已经改变了我对此的看法。您应该安装pry、pry-doc和pry-debug、pry-debugger和pry-rails。然后在您的代码中使用binding.pry打开一个统治世界的交互式调试器控制台！|737229|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|18|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1A|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1E|8|@]|9|@]|A|$E|F]]|$1|U|3|V|5|6|7|1F|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1G|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|D|7|1H|8|@]|9|@]|A|$E|F]]|$1|10|3|11|5|6|7|1I|8|@]|9|@]|A|$]]|$1|12|3|13|5|6|7|1J|8|@]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|15|$]]

The best way I have found to debug in rSpec is by adding the following to your 'spec_helper.rb' file



<pre><code>def logger
 Rails.logger
end
</code></pre>

You can then access all the logger methods within your rSpec files and incorporate such things as tagged logging. This of course is for Rails 3 and up. If you have anything prior to Rails 3 then add this instead:



<pre><code>def logger
 RAILS_DEFAULT_LOGGER
end
</code></pre>

Once you have your logging statements in place you can enter 

<pre><code>tail -f log/test.log
</code></pre>

in your terminal shell in order to watch your logging statements while the tests are run.

Of course in your actual rspec test you would enter something such as



<pre><code>logger.debug "#{1.class}" # =&gt; Fixnum
</code></pre>

If you want to filter your debug statements from the rest of your test log simply prepend a random string on to your debug statement and pipe the output of the tail command to grep.

Example:

<pre><code>logger.debug "random_string #{1.class}" # =&gt; Fixnum

tail -f log/test.log | grep random_string
</code></pre>

<h3>Update</h3>

I've changed my opinion on this. You should install pry, pry-doc, and pry-debug, pry-debugger, and pry-rails. Then use binding.pry in your code to open an interactive debugger console that rules the world!

blocks|key|953353|text|对于Ruby2.0，我使用的是byebug：https://github.com/deivid-rodriguez/byebug|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|953354|gem+'byebug'|code-block|syntax|javascript|953355|代码：|953356|#+spec/models/user_spec.rb
require+'spec_helper'
require+'byebug'

describe+User+do
++it+"should+be+valid"+do
++++byebug
++++User.new.should+be_valid
++end
end|953357|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/deivid-rodriguez/byebug^0|M|16|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|C|$G|H]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

For ruby 2.0 I use byebug: <a href="https://github.com/deivid-rodriguez/byebug">https://github.com/deivid-rodriguez/byebug</a>

<pre><code>gem 'byebug'
</code></pre>

Code:

<pre><code># spec/models/user_spec.rb
require 'spec_helper'
require 'byebug'

describe User do
 it "should be valid" do
 byebug
 User.new.should be_valid
 end
end
</code></pre>

blocks|key|737333|text|最好、最干净的选择是在.rspec文件中使用--require。您放置的内容取决于您使用哪个gem进行调试。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|737334|--color
--require+pry
--require+rails_helper|code-block|syntax|javascript|737335|这些选项对应于命令行选项(-d或--debug现在已弃用)。|737336|您可以随意使用debugger、ruby-debug或pry+(Gemfile中的pry-rails)。|737337|对于您的Gemfile：|737338|group+:test,+:development+do
++gem+'pry-rails'
end|737339|将require+'ruby-debug'等放在您的规范的顶部只是耦合更紧密--特别是因为这里投票最多的注释建议将其单独放在您的所有文件中。使用新的.rspec文件，您不再需要将require+'spec_helper'或require+'rails_helper'放在文件的顶部。|737340|它们作为隐式命令行参数更有意义。|737341|entityMap^0|B|6|M|9|0|0|0|7|8|G|A|R|3|0|0|0|1|K|22|6|2H|L|33|M|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|13|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|14|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1C|8|@]|D|@]|E|$]]|$1|Q|3|R|5|H|7|1D|8|@]|D|@]|E|$I|J]]|$1|S|3|T|5|6|7|1E|8|@$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]|$9|1J|A|1K|B|C]|$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|1N|8|@]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]]|X|$]]

The best and cleanest option is to use <code>--require</code> in your <code>.rspec</code> file. What you put depends on which gem you use for debugging.

<pre><code>--color
--require pry
--require rails_helper
</code></pre>

These correspond to command line options (-d or --debug is now deprecated).

Feel free to use <code>debugger</code>, <code>ruby-debug</code> or <code>pry</code> (pry-rails in your Gemfile).

For your Gemfile:

<pre><code>group :test, :development do
 gem 'pry-rails'
end
</code></pre>

Putting <code>require 'ruby-debug'</code> etc. at the top of your spec is simply more tightly coupled -- especially since here the top voted comment suggests putting it individually in ALL your files. With the new <code>.rspec</code> file you shouldn't need to put <code>require 'spec_helper'</code> or <code>require 'rails_helper'</code> at the top of your files anymore.

They make more sense as implicit command line arguments.

I'm trying to get Ruby debugger running in one of my specs:

<pre><code>describe User do
 it "should be valid" do
 debugger
 User.new.should be_valid
 end
end
</code></pre>

When I run rspec though, I get:

<pre><code>debugger statement ignored, use -d or --debug option to enable debugging
</code></pre>

I've tried the following:

<pre><code>rake spec --debug
rake spec --debug --trace
rake spec:models --debug
bundle exec rspec --debug
bundle exec rspec --debug spec/models/
bundle exec rspec --d spec/models/
bundle exec "rspec --debug" spec/models/
bundle exec rspec --debugger spec/models/
bundle exec --debugger rspec spec/models/
bundle --debugger exec rspec spec/models/
bundle --debugger exec rspec spec/models/
bundle exec --debugger rspec spec/models/
bundle exec rspec --debugger spec/models/
</code></pre>

Any ideas on how to exec rspec in the right way? I'm on Rails 3.0.5, Ruby 1.9.2, RSpec 2.5.1, ruby-debug19.

Thanks,
Justin.

Running ruby debug in rspec?

调试器

我正在尝试让Ruby调试器在我的一个规范中运行：describe User do  it "should be valid" do    debugger    User.new.should be_valid  endend但是，当我运行rspec时，我得到：debugger statement ignored, u...

问在rspec中运行ruby debug？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在rspec中运行ruby debug？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在rspec中运行ruby debug？
EN