blocks|key|1081639|text|使用#instance_eval|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1081640|@controller+=+AccountController.new
@controller.instance_eval{+current_account+}+++#+invoke+the+private+method
@controller.instance_eval{+@current_account+}.should+eql+...+#+check+the+value+of+the+instance+variable|code-block|syntax|javascript|1081641|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Use #instance_eval

<pre><code>@controller = AccountController.new
@controller.instance_eval{ current_account } # invoke the private method
@controller.instance_eval{ @current_account }.should eql ... # check the value of the instance variable
</code></pre>

blocks|key|867040|text|我使用send方法。例如：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|867041|event.send(:private_method).should+==+2|code-block|syntax|javascript|867042|因为"send“可以调用私有方法。|867043|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I use send method. Eg:

<pre><code>event.send(:private_method).should == 2
</code></pre>

Because "send" can call private methods

blocks|key|1081574|text|在哪里使用了current_account方法？它的作用是什么？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1081575|通常，您不测试私有方法，而是测试调用私有方法的方法。|1081576|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Where is the current_account method being used? What purpose does it serve?

Generally, you don't test private methods but rather test the methods that call the private one.

blocks|key|867232|text|您可以将私有或受保护的方法设置为公共方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|867233|MyClass.send(:public,+*MyClass.protected_instance_methods)+
MyClass.send(:public,+*MyClass.private_instance_methods)|code-block|syntax|javascript|867234|只需将此代码放在您的测试类中，替换您的类名即可。如果适用，请包括命名空间。|867235|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You could make you private or protected methods as public:

<pre><code>MyClass.send(:public, *MyClass.protected_instance_methods) 
MyClass.send(:public, *MyClass.private_instance_methods)
</code></pre>

Just place this code in your testing class substituting your class name. Include the namespace if applicable.

blocks|key|1081648|text|require+'spec_helper'

describe+AdminsController+do+
++it+"-current_account+should+return+correct+value"+do
++++class+AccountController
++++++def+test_current_account
++++++++current_account+++++++++++
++++++end
++++end

++++account_constroller+=+AccountController.new
++++account_controller.test_current_account.should+be_correct+++++++++++++

+++end
end|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1081649|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>require 'spec_helper'

describe AdminsController do 
 it "-current_account should return correct value" do
 class AccountController
 def test_current_account
 current_account 
 end
 end

 account_constroller = AccountController.new
 account_controller.test_current_account.should be_correct 

 end
end
</code></pre>

blocks|key|867131|text|单元测试私有方法似乎与应用程序的行为脱离了上下文。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|867132|你会先写你的调用代码吗？在您的示例中不会调用此代码。|867133|其行为是:您希望从另一个对象加载一个对象。|867134|context+"When+I+am+logged+in"
++let(:user)+{+create(:user)+}
++before+{+login_as+user+}

++context+"with+an+account"
++++let(:account)+{+create(:account)+}
++++before+{+user.update_attribute+:account_id,+account.id+}

++++context+"viewing+the+list+of+accounts"+do
++++++before+{+get+:index+}

++++++it+"should+load+the+current+users+account"+do
++++++++assigns(:current_account).should+==+account
++++++end
++++end
++end
end|code-block|syntax|javascript|867135|为什么你想要从你应该尝试描述的行为中脱离上下文来编写测试？|867136|这段代码会在很多地方使用吗？需要更通用的方法吗？|867137|https://www.relishapp.com/rspec/rspec-rails/v/2-8/docs/controller-specs/anonymous-controller|offset|length|867138|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|0|2K|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|12|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|13|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|14|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|15|8|@]|9|@$Q|16|R|17|1|18]]|A|$]]|$1|S|3|-4|5|6|7|19|8|@]|9|@]|A|$]]]|T|$U|$5|V|W|X|A|$Y|P]]]]

Unit testing private methods seems too out of context with the behaviour of the application.

Are you writing your calling code first?
This code is not called in your example.

The behaviour is: you want an object loaded from another object.

<pre><code>context "When I am logged in"
 let(:user) { create(:user) }
 before { login_as user }

 context "with an account"
 let(:account) { create(:account) }
 before { user.update_attribute :account_id, account.id }

 context "viewing the list of accounts" do
 before { get :index }

 it "should load the current users account" do
 assigns(:current_account).should == account
 end
 end
 end
end
</code></pre>

Why do u want to write the test out of context from the behaviour you
should be trying to describe?

Does this code get used in a lot of places?
Need a more generic approach?

<a href="https://www.relishapp.com/rspec/rspec-rails/v/2-8/docs/controller-specs/anonymous-controller" rel="nofollow">https://www.relishapp.com/rspec/rspec-rails/v/2-8/docs/controller-specs/anonymous-controller</a>

blocks|key|1081876|text|使用rspec-context-private+gem在上下文中临时使私有方法成为公共方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1081877|gem+'rspec-context-private'|code-block|syntax|javascript|1081878|它的工作方式是将共享上下文添加到项目中。|1081879|RSpec.shared_context+'private',+private:+true+do

++before+:all+do
++++described_class.class_eval+do
++++++@original_private_instance_methods+=+private_instance_methods
++++++public+*@original_private_instance_methods
++++end
++end

++after+:all+do
++++described_class.class_eval+do
++++++private+*@original_private_instance_methods
++++end
++end

end|1081880|然后，如果将:private作为元数据传递给describe块，则私有方法将在该上下文中是公共的。|style|CODE|1081881|describe+AccountController,+:private+do
++it+'can+test+private+methods'+do
++++expect{subject.current_account}.not_to+raise_error
++end
end|1081882|entityMap|0|LINK|mutability|MUTABLE|url|http://github.com/barelyknown/rspec-context-private^0|2|P|0|0|0|0|0|6|8|M|8|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@$A|11|B|12|1|13]]|C|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|15|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|16|8|@]|9|@]|C|$G|H]]|$1|M|3|N|5|6|7|17|8|@$A|18|B|19|O|P]|$A|1A|B|1B|O|P]]|9|@]|C|$]]|$1|Q|3|R|5|F|7|1C|8|@]|9|@]|C|$G|H]]|$1|S|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|T|$U|$5|V|W|X|C|$Y|Z]]]]

Use the <a href="http://github.com/barelyknown/rspec-context-private" rel="nofollow">rspec-context-private gem</a> to temporarily make private methods public within a context.

<pre><code>gem 'rspec-context-private'
</code></pre>

It works by adding a shared context to your project.

<pre><code>RSpec.shared_context 'private', private: true do

 before :all do
 described_class.class_eval do
 @original_private_instance_methods = private_instance_methods
 public *@original_private_instance_methods
 end
 end

 after :all do
 described_class.class_eval do
 private *@original_private_instance_methods
 end
 end

end
</code></pre>

Then, if you pass <code>:private</code> as metadata to a <code>describe</code> block, the private methods will be public within that context.

<pre><code>describe AccountController, :private do
 it 'can test private methods' do
 expect{subject.current_account}.not_to raise_error
 end
end
</code></pre>

blocks|key|867277|text|我知道这有点老生常谈，但是如果你希望这些方法可以通过rspec测试，但在prod中不可见，那么它是有效的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|867278|class+Foo
++def+public_method
++++#some+stuff
++end

++eval('private')+unless+Rails.env+==+'test'

++def+testable_private_method
++++#+You+can+test+me+if+you+set+RAILS_ENV=test
++end+
end|code-block|syntax|javascript|867279|现在，当您可以运行时，您的规范如下所示：|867280|RAILS_ENV=test+bundle+exec+rspec+spec/foo_spec.rb+|867281|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I know this is kinda hacky, but it works if you want the methods testable by rspec but not visible in prod.

<pre><code>class Foo
 def public_method
 #some stuff
 end

 eval('private') unless Rails.env == 'test'

 def testable_private_method
 # You can test me if you set RAILS_ENV=test
 end 
end
</code></pre>

Now when you can run you're spec like so:

<pre><code>RAILS_ENV=test bundle exec rspec spec/foo_spec.rb 
</code></pre>

blocks|key|866947|text|如果需要测试私有函数，请创建一个调用私有函数的公共方法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|866948|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you need to test a private function create a public method that invokes the private one.

I have controller:

<pre><code>class AccountController &lt; ApplicationController
 def index
 end

 private
 def current_account
 @current_account ||= current_user.account
 end
end
</code></pre>

How to test private method <code>current_account</code> with rspec?

P.S. I use Rspec2 and Ruby on Rails 3

Rspec, Rails: how to test private methods of controllers?

单元测试

我有控制器：class AccountController < ApplicationController def index end private def current_account @current_account ||= current_user.account endend如何使用rspec测试私有方法current_account？附言:我使用Rspec2和Ruby

问Rails:如何测试控制器的私有方法？
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Rails:如何测试控制器的私有方法？EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Rails:如何测试控制器的私有方法？
EN