Capybara 问题：@request 必须是 ActionDispatch::Request

Question

我在让 Capybara 与 Rails 一起使用时遇到问题。只是测试那个所谓有趣的测试东西。好的，在所附的代码中有几个等效的测试。第一个是用Rails 自带的shoulda-context + Test::Unit 制作的。第二个测试也是使用水豚和shoulda-context 进行的。

require 'integration_test_helper'

class UsersTest < ActionDispatch::IntegrationTest
  fixtures :all

  context "signup" do

    context "failure" do

      setup do
      @attr = { :name => "", :email => "", :password => "", :password_confirmation => "" }
      end

      should "not make a new user" do
        assert_no_difference 'User.count' do
          post_via_redirect "users", :user =>@attr  # enviem les dades d'un nou usuari via create (POST /users)
          assert_template 'users/new'     # ens retorna a users/new, que significa que no s'ha creat l'usuari
          assert_select "div#error_explanation" # comprovem que conte missatges d'error
        end
      end

      should "not make a new user (capybara)" do
        assert_no_difference 'User.count' do
          visit '/signup'
          fill_in 'Name', :with => @attr[:name]
          fill_in 'Email', :with => @attr[:email]
          fill_in 'Password', :with => @attr[:password]
          fill_in 'Confirmation', :with => @attr[:password_confirmation]
          click_button 'Sign Up!'
          assert_template 'users/new'     # ens retorna a users/new, que significa que no s'ha creat l'usuari
          assert_select "div#error_explanation" # comprovem que conte missatges d'error
        end
      end
    end
end

虽然第一个工作正常，但水豚会抛出此错误消息：

================================================================================
Error:
test: signup failure should not make a new user (capybara). (UsersTest):
ArgumentError: @request must be an ActionDispatch::Request
    test/integration/users_test.rb:30:in `block (4 levels) in <class:UsersTest>'
    test/integration/users_test.rb:23:in `block (3 levels) in <class:UsersTest>'
================================================================================

所需的 *integration_test_helper.rb* 文件是我在谷歌搜索中发现的所有假定解决方案的累加器，但对我来说不起作用。

require 'test_helper'
require 'capybara/rails'
require 'database_cleaner'

# Transactional fixtures do not work with Selenium tests, because Capybara
# uses a separate server thread, which the transactions would be hidden
# from. We hence use DatabaseCleaner to truncate our test database.
DatabaseCleaner.strategy = :truncation

class ActionDispatch::IntegrationTest
  # Make the Capybara DSL available in all integration tests
  include Capybara::DSL

  # Stop ActiveRecord from wrapping tests in transactions
  self.use_transactional_fixtures = false

  teardown do
    DatabaseCleaner.clean       # Truncate the database
    Capybara.reset_sessions!    # Forget the (simulated) browser state
    Capybara.use_default_driver # Revert Capybara.current_driver to Capybara.default_driver
  end
end

有人有解决办法吗？我应该尝试其他集成框架，例如 webrat 吗？

我的设置是：

marcel@pua:~/Desenvolupament/Rails3Examples/ror_tutorial$ rake about
About your application's environment
Ruby version              1.9.2 (x86_64-linux)
RubyGems version          1.8.15
Rack version              1.3
Rails version             3.1.3
JavaScript Runtime        therubyracer (V8)
Active Record version     3.1.3
Action Pack version       3.1.3
Active Resource version   3.1.3
Action Mailer version     3.1.3
Active Support version    3.1.3
Middleware                ActionDispatch::Static, Rack::Lock, #<ActiveSupport::Cache::Strategy::LocalCache::Middleware:0x00000002b9bac0>, Rack::Runtime, Rack::MethodOverride, Rails::Rack::Logger, ActionDispatch::ShowExceptions, ActionDispatch::RemoteIp, Rack::Sendfile, ActionDispatch::Reloader, ActionDispatch::Callbacks, ActiveRecord::ConnectionAdapters::ConnectionManagement, ActiveRecord::QueryCache, ActionDispatch::Cookies, ActionDispatch::Session::CookieStore, ActionDispatch::Flash, ActionDispatch::ParamsParser, ActionDispatch::Head, Rack::ConditionalGet, Rack::ETag, ActionDispatch::BestStandardsSupport
Application root          /mnt/dropbox/Dropbox/DESENVOLUPAMENT/Rails3Examples/ror_tutorial
Environment               development
Database adapter          sqlite3
Database schema version   20120127011330

也

shoulda-context (1.0.0)
capybara (1.1.2)

谢谢

Answer 1

您混淆了测试类型并尝试在错误的测试类型中断言模板。您应该只在功能测试中断言模板，其中您只是直接测试控制器而不是实际模拟用户交互。

Capybara 专门用于集成测试，本质上是从最终用户与浏览器交互的角度运行测试。在这些测试中，您不应该断言模板，因为最终用户无法深入了解您的应用程序。相反，您应该测试的是某个操作是否能让您走上正确的道路。

current_path.should == new_user_path
page.should have_selector('div#error_explanation')

请参阅 git 上的 Capybara 自述文件中的“DSL”部分：https://github.com/jnicklas/capybara

针对您的问题的官方说明：https://github.com/jnicklas/capybara/issues/240

Answer 2

为了我的完整性，因为我知道我会一遍又一遍地回到这个链接：

那些使用测试单元和水豚的人，这也是一个很好的入门读物：来自 techiferous。

请注意 assert page.has_content?("something") 的使用，

这与 assert_equal some_path, current_path 一样可以很好地用于测试路由。

它是否是最完整的，不知道，但你不需要更多。

Answer 3

感谢您的提示@Ryan。我试图弄清楚如何翻译 http:// 中的一些 RSpec 集成测试示例ruby.railstutorial.org/chapters/sign-up#sec:rspec_integration_tests 进入 Test::Unit + Capybara。原始的 RSpec 集成测试是

it "should not make a new user" do
  lambda do
      visit signup_path
      fill_in "Name",         :with => ""
      fill_in "Email",        :with => ""
      fill_in "Password",     :with => ""
      fill_in "Confirmation", :with => ""
      click_button
      response.should render_template('users/new')
      response.should have_selector("div#error_explanation")
    end.should_not change(User, :count)
  end
end

因此，在您回答之后，我认为原始示例不应包含 response.should render_template('users/new')