Hartl的Ruby on Rails教程测试失败（第9章）

Question

我正在研究Hartl着名的Ruby on Rails 4教程。 我对Rails并不陌生，但是对测试却不陌生：RSpec，Capybara，FactoryGirl等。我在编辑第9章（ http://ruby.railstutorial.com）中的用户时遇到了一些测试方面的问题。 org / chapters / updating-showing-and-deleting-users＃sec-successful_edits ）。 我将首先发布我试图纠正的内容，然后发布相关代码：

1. 与本教程相比，三重检查了我的代码。 一切看起来都很好，但我可能会丢失一些东西。
2. 重新启动我的服务器，然后重置，重新填充并重新设置测试数据库。
3. 使用FF中的SQLite Manager扩展检查了测试和开发SQLite数据库中的用户。

错误如下：

1) Authentication Signin page with valid information followed by signout 
 Failure/Error: before { click_link "Sign Out" }
 Capybara::ElementNotFound:
   Unable to find link "Sign Out"
 # ./spec/requests/authentication_pages_spec.rb:41:in `block (5 levels) in <top (required)>'

 2) UserPages edit with invalid information 
 Failure/Error: before { click_button "Save changes" }
 Capybara::ElementNotFound:
   Unable to find button "Save changes"
 # ./spec/requests/user_pages_spec.rb:130:in `block (4 levels) in <top (required)>'

3) UserPages edit page 
 Failure/Error: it { should have_title("Edit user") }
   expected #has_title?("Edit user") to return true, got false
 # ./spec/requests/user_pages_spec.rb:125:in `block (4 levels) in <top (required)>'

4) UserPages edit page 
 Failure/Error: it { should have_content("Update your profile") }
   expected #has_content?("Update your profile") to return true, got false
 # ./spec/requests/user_pages_spec.rb:124:in `block (4 levels) in <top (required)>'

5) UserPages edit page 
 Failure/Error: it { should have_link('change', href: 'http://gravatar.com/emails') }
   expected #has_link?("change", {:href=>"http://gravatar.com/emails"}) to return true, got false
 # ./spec/requests/user_pages_spec.rb:126:in `block (4 levels) in <top (required)>'

6) UserPages edit with valid information 
 Failure/Error: fill_in "Name",             with: new_name
 Capybara::ElementNotFound:
   Unable to find field "Name"
 # ./spec/requests/user_pages_spec.rb:138:in `block (4 levels) in <top (required)>'

7) UserPages edit with valid information 
 Failure/Error: fill_in "Name",             with: new_name
 Capybara::ElementNotFound:
   Unable to find field "Name"
 # ./spec/requests/user_pages_spec.rb:138:in `block (4 levels) in <top (required)>'

8) UserPages edit with valid information 
 Failure/Error: fill_in "Name",             with: new_name
 Capybara::ElementNotFound:
   Unable to find field "Name"
 # ./spec/requests/user_pages_spec.rb:138:in `block (4 levels) in <top (required)>'

9) UserPages edit with valid information 
 Failure/Error: fill_in "Name",             with: new_name
 Capybara::ElementNotFound:
   Unable to find field "Name"
 # ./spec/requests/user_pages_spec.rb:138:in `block (4 levels) in <top (required)>'

10) UserPages edit with valid information 
 Failure/Error: fill_in "Name",             with: new_name
 Capybara::ElementNotFound:
   Unable to find field "Name"
 # ./spec/requests/user_pages_spec.rb:138:in `block (4 levels) in <top (required)>'

最初，我认为这是水豚问题，但是我不确定。 这是测试代码（位于./spec/requests/user_pages_spec.rb中）：

describe "edit", :js => true do
  let(:user) { FactoryGirl.create(:user) }
  before do
    sign_in user
    visit edit_user_path(user)
  end

  describe "page" do
    it { should have_content("Update your profile") }
    it { should have_title("Edit user") }
    it { should have_link('change', href: 'http://gravatar.com/emails') }
  end

  describe "with invalid information" do
    before { click_button "Save changes" }
    it { should have_content('error') }
  end

  describe "with valid information" do
    let(:new_name)  { "New Name" }
    let(:new_email) { "new@example.com" }
    before do
      fill_in "Name",             with: new_name
      fill_in "Email",            with: new_email
      fill_in "Password",         with: user.password
      fill_in "Confirm Password", with: user.password
      click_button "Save changes"
    end

    it { should have_title(new_name) }
    it { should have_selector('div.alert.alert-success') }
    it { should have_link('Sign Out', href: signout_path) }
    specify { expect(user.reload.name).to  eq new_name }
    specify { expect(user.reload.email).to eq new_email }
  end
end

我添加到初始描述块:js => true因为我认为这是Capybara的问题，并且页面加载速度过快，但是，添加该哈希值会导致FF浏览器打开，我可以观察到发生了什么... FactoryGirl已成功创建用户，但是尝试登录时收到无效的电子邮件或密码错误。因此，登录失败，因此所有测试都无法通过编辑表单。 这是相关的FactoryGirl代码：

./spec/utilities.rb中的sign_in（）帮助器：

def sign_in(user, options={})
  if options[:no_capybara]
    # Sign in when not using Capybara.
    remember_token = User.new_remember_token
    cookies[:remember_token] = remember_token
    user.update_attribute(:remember_token, User.encrypt(remember_token))
  else
    visit signin_path
    fill_in "Email",    with: user.email
    fill_in "Password", with: user.password
    click_button "Sign In"
  end
end

./spec/factories.rb：

FactoryGirl.define do
  factory :user do
    sequence(:name)  { |n| "Person #{n}" }
    sequence(:email) { |n| "person_#{n}@example.com"}
    password "foobar"
    password_confirmation "foobar"

    factory :admin do
      admin true
    end
  end
end

我已经正确安装了gem，FactoryGirl在其他测试中似乎可以正常工作，这是gemfile：

group :test do
  gem 'selenium-webdriver', '2.35.1'
  gem 'capybara', '2.1.0'
  gem 'growl', '1.0.3'
  gem 'factory_girl_rails', '4.2.1'
end

就像我说的那样，我查看了SQLite开发和测试数据库，但在测试数据库中没有看到任何用户。 FactoryGirl是否仅临时创建测试用户，然后在完成后回滚？ 是什么导致我看到的失败标志？ 还是我还缺少其他东西？

如果有人问，这里是相关的观点：

edit.html.erb：

<% provide(:title, "Edit user") %>
<h1>Update your profile</h1>

<div class="row">
  <div class="span6 offset3">
    <%= form_for(@user) do |f| %>
    <%= render 'shared/error_messages' %>

    <%= f.label :name %>
    <%= f.text_field :name %>

    <%= f.label :email %>
    <%= f.email_field :email %>

    <%= f.label :password %>
    <%= f.password_field :password %>

    <%= f.label :password_confirmation, "Confirm Password" %>
    <%= f.password_field :password_confirmation %>

    <%= f.submit "Save changes", class: "btn btn-large btn-primary" %>
  <% end %>

  <%= gravatar_for @user %>
  <a href="http://gravatar.com/emails">change</a>
</div>

以及在application.html.erb中呈现的_header.html.erb

<header class="navbar navbar-fixed-top navbar-inverse">
  <div class="navbar-inner">
    <div class="container">
      <%= link_to "sample app", root_path, id: "logo" %>
      <nav>
        <ul class="nav pull-right">
          <li><%= link_to "Home", root_path %></li>
          <li><%= link_to "Help", help_path %></li>
          <% if signed_in? %>
            <li><%= link_to "Users", users_path %></li>
            <li id="fat-menu" class="dropdown">
              <a href="#" class="dropdown-toggle" data-toggle="dropdown">
                Account <b class="caret"></b>
              </a>
              <ul class="dropdown-menu">
                <li><%= link_to "Profile", current_user %></li>
                <li><%= link_to "Settings", edit_user_path(current_user) %></li>
                <li class="divider"></li>
                <li>
                  <%= link_to "Sign Out", signout_path, method: "delete" %>
                </li>
              </ul>
            </li>
          <% else %>
            <li><%= link_to "Sign In", signin_path %></li>
          <% end %>
        </ul>
      </nav>
    </div>
  </div>
</header>

Answer 1

您遇到的第一个错误很可能是因为您需要将describe "followed by signout"嵌套在describe "after saving the user"如下所示：

 describe "after saving the user" do
        before { click_button submit }
        let(:user) { User.find_by(email: 'user@example.com') }

        it { should have_link('Sign out') }
        it { should have_title(user.name) }
        it { should have_selector('div.alert.alert-success', text: 'Welcome') }
        describe "followed by signout" do #Notice that this describe is inside the other one
            before { click_link "Sign out" }
            it { should have_link('Sign in') }
        end
end

我知道这只是部分答案，但是很难一次解决所有问题。 解决此问题后，请再次运行测试，并告诉我留下了哪些错误代码。 我会尽力帮助您。

（至少如果这解决了您的第一个问题，则可能是其他问题）