blocks|key|3195916|text|为什么您觉得有必要测试这些路由？纯粹为了确保routes.rb中定义的路由能够正常工作？如果是这样，那就不要这样做。确保框架内部正常运行不是应用程序测试的工作，而是Rails框架自己测试的工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3195917|如果您想要测试某种动态/用户可定义的路由，我可能会选择集成。|3195918|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|$]]

Why do you feel the need to test the routes? Purely to make sure that the routes defined in your routes.rb actually work? If so, then don't. That's not the job of your application's tests to make sure that the framework's internals operate properly - that's the job of the Rails framework's own tests.

If perhaps you have some sort of dynamic/user definable route that you want to test, I'd probably go with integration.

blocks|key|278137|text|路由应该作为集成测试的一部分来完成。集成测试是测试应用程序的重要工作流程的地方-更具体地说，是否定义了URL似乎是一个重要的工作流程。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|278138|您的集成测试将看起来像任何normal+integration+test|offset|length|278139|#+/tests/integration/routes_test.rb
require+'test_helper'

class+RoutesTest+<+ActionController::IntegrationTest
++test+"route+test"+do
++++assert_generates+"/photos/1",+{+:controller+=>+"photos",+:action+=>+"show",+:id+=>+"1"+}
++++assert_generates+"/about",+:controller+=>+"pages",+:action+=>+"about"
++end
end|code-block|syntax|javascript|278140|至于@jemminger对不测试路由的回应--虽然验证routes.rb工作的是Rail的测试，但测试你的路由中是否定义了http://yoursite.com/users并不是Rail的责任。需要注意的是，大多数路由测试可以在现有的集成测试中完成，所以针对路由的特定测试可能是多余的。|style|CODE|278141|我能想到的具体用例是所有已经或将要从Rails2升级到Rails3的人。定义路由的代码已经发生了重大变化，最好是从测试中发现路由升级正确，而不是用户报告404错误时。|278142|entityMap|0|LINK|mutability|MUTABLE|url|http://guides.rubyonrails.org/testing.html#integration-testing|1|https://stackoverflow.com/questions/5290245/where-to-test-routes-in-ruby-on-rails/5290729#5290729^0|0|D|N|0|0|0|1P|P|2|A|1|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|F|3|G|5|H|7|15|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|16|8|@$D|17|E|18|M|N]]|9|@$D|19|E|1A|1|1B]]|A|$]]|$1|O|3|P|5|6|7|1C|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]|Y|$5|T|U|V|A|$W|Z]]]]

Routes should be done as part of integration tests. Integration tests are where you test the important work flows of your application - more specifically whether a URL is defined or not seems to be an important workflow.

Your integration test would look like any <a href="http://guides.rubyonrails.org/testing.html#integration-testing" rel="nofollow noreferrer">normal integration test</a>:

<pre><code># /tests/integration/routes_test.rb
require 'test_helper'

class RoutesTest &lt; ActionController::IntegrationTest
 test "route test" do
 assert_generates "/photos/1", { :controller =&gt; "photos", :action =&gt; "show", :id =&gt; "1" }
 assert_generates "/about", :controller =&gt; "pages", :action =&gt; "about"
 end
end
</code></pre>

As to <a href="https://stackoverflow.com/questions/5290245/where-to-test-routes-in-ruby-on-rails/5290729#5290729">@jemminger</a>'s response of not testing routes - While it is Rail's tests that verify that routes.rb works, it's not Rail's responsibility to test whether <code>http://yoursite.com/users</code> is defined in your routes. The caveat is that most route testing could be done in existing integration tests, so specific tests for routes could be redundant.

The specific use case I can think of are all the people that have already, or are going to upgrade from Rails 2 to Rails 3. The code to define routes has changed significantly, and it's better to find out from tests that the routes were upgraded correctly, than from users when they report 404 errors.

blocks|key|2982669|text|根据this+rails+bug的一条评论，合适的地方是在功能测试中。如果您尝试在集成测试中对它们进行测试，则在routes.rb中建立的路由将不可用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2982670|require+'test_helper'

class+FooControllerTest+<+ActionController::TestCase
++test+"foo+routes"+do
++++assert_recognizes({:controller+=>+'foo_controller',+:action+=>+'list'},+'/foos'
++end
end|code-block|syntax|javascript|2982671|路由测试是列出存在于野外的链接的好地方，并避免因代码更改而无意中破坏它们。有点奇怪的是，测试的范围是一个控制器，因为它是你实际测试的整个路由集，但我还没有听说过“路由集测试”。|2982672|entityMap|0|LINK|mutability|MUTABLE|url|https://rails.lighthouseapp.com/projects/8994/tickets/4390-patch-assert_recognizes-should-work-in-integration-tests^0|1K|9|2|E|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@$9|V|A|W|B|C]]|D|@$9|X|A|Y|1|Z]]|E|$]]|$1|F|3|G|5|H|7|10|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|11|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|12|8|@]|D|@]|E|$]]]|N|$O|$5|P|Q|R|E|$S|T]]]]

According to a comment in <a href="https://rails.lighthouseapp.com/projects/8994/tickets/4390-patch-assert_recognizes-should-work-in-integration-tests" rel="nofollow">this rails bug</a>, the proper place is in a functional test. If you try to test them in an integration test, the routes you established in <code>routes.rb</code> will not be available.

<pre><code>require 'test_helper'

class FooControllerTest &lt; ActionController::TestCase
 test "foo routes" do
 assert_recognizes({:controller =&gt; 'foo_controller', :action =&gt; 'list'}, '/foos'
 end
end
</code></pre>

Route tests are good places to list links that exist in the wild, and avoid inadvertently breaking them with a code change. It's a little strange that the tests are scoped to a controller, since it's the route set as a whole you're actually testing, but I haven't heard of a 'route set test'.

blocks|key|274582|text|我建议您为测试/控制器文件夹中的路由创建一个测试文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|274583|class+HomeRoutesTest+<+ActionController::TestCase

++test+"must+route+to+home+index"+do
++++assert_routing+'/',+controller:+"home",+action:+"index"
++end

end|code-block|syntax|javascript|274584|有人提到，它们属于集成测试。我不同意。您只是测试路由，仅此而已。因此，它宁愿进行功能测试，甚至单元测试，而不是集成测试。|274585|您可以在Rails+RailsGuide+Testing,+section+9.+++Testing+Routes中找到参考资料|offset|length|274586|274587|集成测试是针对流程的，您可以在其中测试不同控制器操作的交互，例如执行业务流程，如用户登录、浏览站点和将项目放入篮子中。也就是说，如果您的路由不起作用，那么集成测试就不会起作用。因此，许多人说集成测试是测试路由的地方。但是，考虑到开发周期，在进行集成测试之前，您需要先创建单元测试、控制器测试、路由测试等。|274588|另外，assert_routing做了两个测试：assert_generates和assert_recognizes。|style|CODE|274589|entityMap|0|LINK|mutability|MUTABLE|url|http://guides.rubyonrails.org/testing.html#testing-routes^0|0|0|0|A|1B|0|0|0|0|3|E|O|G|15|H|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|12|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|13|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|14|8|@]|9|@$K|15|L|16|1|17]]|A|$]]|$1|M|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|19|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1A|8|@$K|1B|L|1C|R|S]|$K|1D|L|1E|R|S]|$K|1F|L|1G|R|S]]|9|@]|A|$]]|$1|T|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]]|U|$V|$5|W|X|Y|A|$Z|10]]]]

I suggest you create a test file for the routes in your test/controllers folder.

<pre><code>class HomeRoutesTest &lt; ActionController::TestCase

 test "must route to home index" do
 assert_routing '/', controller: "home", action: "index"
 end

end
</code></pre>

It was mentioned that they belong to integration test. I disagree. You merely test routes, that's it. So it would rather fall into functional or even unit testing instead of integration testing.

<blockquote>
 You can find a reference in the Rails <a href="http://guides.rubyonrails.org/testing.html#testing-routes" rel="noreferrer">RailsGuide Testing, section 9.
 Testing Routes</a>
</blockquote>

Integration tests are for the flow, where you test the interaction of different controller action, e.g. executing a business process like user logs in, browses the site and puts an item into the basket.
That said your integration tests won't work if your routes don't work. Thus many say that integration tests is the place where you test routes.
However, considering the development cycle, you would create unit tests, controller tests, route tests, etc. first before doing the integration tests.

And on another note: <code>assert_routing</code> does both tests: <code>assert_generates</code> and <code>assert_recognizes</code>.

blocks|key|274600|text|如果您使用的是rspec，那么最自然的路由测试位置是spec/routing目录。来自The+Rspec+documentation|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|274601|274602|路由规范由:type+=>+:routing标记，或者如果您已通过将它们放在spec/+Routing中来设置config.infer_spec_type_from_file_location!，则将其标记为。|blockquote|274603|274604|entityMap|0|LINK|mutability|MUTABLE|url|https://www.relishapp.com/rspec/rspec-rails/docs/routing-specs^0|Q|C|17|N|0|0|0|5|H|1J|16|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@$9|V|A|W|1|X]]|E|$]]|$1|F|3|-4|5|6|7|Y|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]]|D|@]|E|$]]|$1|J|3|-4|5|6|7|14|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|15|8|@]|D|@]|E|$]]]|L|$M|$5|N|O|P|E|$Q|R]]]]

If you are using rspec, then the most natural place for routing tests is in the directory <code>spec/routing</code>. From <a href="https://www.relishapp.com/rspec/rspec-rails/docs/routing-specs" rel="nofollow noreferrer">The Rspec documentation</a>:

<blockquote>
 Routing specs are marked by <code>:type =&gt; :routing</code> or if you have set
 <code>config.infer_spec_type_from_file_location!</code> by placing them in spec/routing.
</blockquote>

Where to test routes in ruby on rails?

<ul>
<li>unit tests?</li>
<li>functional tests?</li>
<li>integration tests?</li>
</ul>

Addition:

To be exact, where to apply assertions described <a href="http://guides.rubyonrails.org/routing.html#testing-routes" rel="noreferrer">on guides</a> and <a href="http://api.rubyonrails.org/classes/ActionDispatch/Assertions/RoutingAssertions.html" rel="noreferrer">on api</a>?

Where to test routes in ruby on rails

单元测试

集成测试

路由

在ruby on rails中哪里可以测试路由？单元测试-添加：准确地说，在何处应用和描述的断言

问在ruby on rails中测试路由的位置
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在ruby on rails中测试路由的位置EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在ruby on rails中测试路由的位置
EN