【问题标题】:Ruby on Rails Tutorial - Chapter 9: Missing template updateRuby on Rails 教程 - 第 9 章:缺少模板更新
【发布时间】:2012-09-24 00:47:27
【问题描述】:

我刚刚读完 Michael Hartl 的《Ruby on Rails 教程》一书的Section 9.3 - Unsuccessful Edits。我已经尝试了好几个小时来弄清楚为什么我不能让测试通过检查不成功的编辑。

这是我为本章添加的代码:

spec/requests/authentication_pages_spec.rb

require 'spec_helper'

describe "Authentication" do

  subject { page }

  describe "signin page" do
    before { visit signin_path }

    it { should have_selector('h1',    text: 'Sign in') }
    it { should have_selector('title', text: 'Sign in') }
  end

  describe "signin" do
    before { visit signin_path }

    describe "with invalid information" do
      before { click_button "Sign in" }

      it { should have_selector('title', text: 'Sign in') }
      it { should have_error_message('Invalid') }

      describe "after visiting another page" do
        before { click_link "Home" }
        it { should_not have_error_message }
      end
    end

    describe "with valid information" do
     let(:user) { FactoryGirl.create(:user) }
      before { sign_in user }

      it { should have_selector('title', text: user.name) }
      it { should have_link('Profile',  href: user_path(user)) }
      it { should have_link('Settings', href: edit_user_path(user)) }
      it { should have_link('Sign out', href: signout_path) }
      it { should_not have_link('Sign in', href: signin_path) } 

      describe "followed by signout" do
        before { click_link "Sign out" }
        it { should have_link('Sign in') }
      end
    end
  end
end

spec/requests/user_pages_spec.rb:

require 'spec_helper'

describe "User pages" do

  subject { page }

  describe "signup page" do
    before { visit signup_path }

    it { should have_selector('h1',    text: 'Sign up') }
    it { should have_selector('title', text: 'Sign up') }
  end

  describe "profile page" do
    let(:user) { FactoryGirl.create(:user) }
    before { visit user_path(user) }

    it { should have_selector('h1',    text: user.name) }
    it { should have_selector('title', text: user.name) }
  end

  describe "signup" do

    before { visit signup_path }

    let(:submit) { "Create my account" }
    describe "with invalid information" do
      it "should not create a user" do
        expect { click_button submit }.not_to change(User, :count)
      end

      describe "after submission" do
        before { click_button submit }

        it { should have_selector('title', text: 'Sign up') }
        it { should have_content("Name can't be blank") }
        it { should have_content("Email can't be blank") }
        it { should have_content("Email is invalid") }
        it { should have_content("Password can't be blank") }
        it { should have_content("Password is too short") }
        it { should have_content("Password confirmation can't be blank") }
      end
    end

    describe "with valid information" do
      before do
        fill_in "Name",         with: "Example User"
        fill_in "Email",        with: "user@example.com"
        fill_in "Password",     with: "foobar"
        fill_in "Confirmation", with: "foobar"
      end

      it "should create a user" do
        expect { click_button submit }.to change(User, :count).by(1)
      end

      describe "after saving the user" do
        before { click_button submit }
        let(:user) { User.find_by_email('user@example.com') }
        it { should have_selector('title', text: user.name) }
        it { should have_selector('div.alert.alert-success', text: 'Welcome') }

        it { should have_link('Sign out') }
      end
    end
  end

  describe "edit" do
    let(:user) { FactoryGirl.create(:user) }
    before { visit edit_user_path(user) }

    describe "page" do
      it { should have_selector('h1',    text: "Update your profile") }
      it { should have_selector('title', text: "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
  end
end

spec/support/utilities.rb:

include ApplicationHelper

def full_title(page_title)
  base_title = "Ruby on Rails Tutorial Sample App"
  if page_title.empty?
    base_title
  else
    "#{base_title} | #{page_title}"
  end
end

def valid_signin(user)
  fill_in "Email",    with: user.email
  fill_in "Password", with: user.password
  click_button "Sign in"
end

def sign_in(user)
  visit signin_path
  fill_in "Email",    with: user.email
  fill_in "Password", with: user.password
  click_button "Sign in"
  # Sign in when not using Capybara as well.
  cookies[:remember_token] = user.remember_token
end

RSpec::Matchers.define :have_error_message do |message|
  match do |page|
    page.should have_selector('div.alert.alert-error', text: message)
  end
end

app/controllers/users_controllers.rb:

class UsersController < ApplicationController

  def show
    @user = User.find(params[:id])
  end

  def new
    @user = User.new
  end

  def create
    @user = User.new(params[:user])
    if @user.save
      sign_in @user
      flash[:success] = "Welcome to the Sample App!"
      redirect_to @user
    else
      render 'new'
    end
  end

  def edit
    @user = User.find(params[:id])
  end

  def update
    @user = User.find(params[:id])
    if @user.update_attributes(params[:user])
      # Handle a successful update.
    else
      render 'edit'
    end
  end  
end

app/models/users.rb

class User < ActiveRecord::Base
  attr_accessible :email, :name, :password, :password_confirmation
  has_secure_password

  before_save { self.email.downcase! }
  before_save :create_remember_token

  # Validate that a name is not blank and is no longer than50 characters
  validates :name, presence: true, length: { maximum: 50 }

  # Validate that an email address is not blank, contains a valid pattern, and 
  # is not already in the database
  VALID_EMAIL_REGEX = /\A[\w+\-.]+@[a-z\d\-.]+\.[a-z]+\z/i
  validates :email, presence: true, 
                    format: { with: VALID_EMAIL_REGEX },
                    uniqueness: { case_sensitive: false } 

  #Validate the password is there and is at least 6 characters
  validates :password, length: { minimum: 6 }, on: :create
  validates :password_confirmation, presence: true, on: :create

  # Everything below this private is only visibile to this user model
  private

    # Creates a remember token for the user (not a local variable)
    # Used to keep a user login active indefinitely after sign in
    def create_remember_token
      self.remember_token = SecureRandom.urlsafe_base64
    end
end

app/views/layouts/_header.html.erb

<header class="navbar navbar-fixed-top">
  <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", '#' %></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>

app/views/users/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.text_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>
</div>

我收到以下错误:

Failures:

  1) User pages edit with invalid information 
     Failure/Error: before { click_button "Save changes" }
     ActionView::MissingTemplate:
       Missing template users/update, application/update with {:locale=>[:en], :formats=>[:html], :handlers=>[:erb, :builder, :coffee]}. Searched in:
         * "/home/cbachich/Development/rails_projects/sample_app/app/views"
     # (eval):2:in `click_button'
     # ./spec/requests/user_pages_spec.rb:79:in `block (4 levels) in <top (required)>'

Finished in 2.65 seconds
67 examples, 1 failure

Failed examples:

rspec ./spec/requests/user_pages_spec.rb:81 # User pages edit with invalid information 

【问题讨论】:

    标签: ruby-on-rails rspec


    【解决方案1】:

    如果用户更新成功,您的控制器不会做任何事情,这意味着 Rails 将呈现用户/更新视图。由于您没有此视图,这就是您看到的错误。 Saverio 的注释很好 - 您应该添加一个 redirect_to 才能进入表演动作。这样就可以消除这个错误了。

    但是还有一个更大的问题。为什么您的控制器在您期望它采用失败路径并呈现编辑视图时却采用成功的更新路径?

    根据我的经验,编辑页面填写电子邮件和电子邮件,但将密码留空。您希望更新失败,因为没有密码,但更新成功。为什么?如果您查看模型,您的密码验证只有on: :create。这意味着不会对更新执行这些验证。您希望在更新时执行密码验证,但事实并非如此,这就是编辑成功而不是失败的原因。

    如果您更新模型以对创建和更新操作执行这些验证(可能类似于 on: { :create, :update } ),您应该重新开始工作。您使用无效数据的更新将会失败。

    【讨论】:

    • 这听起来像是我的问题。我今晚回家后测试一下。
    • 这行得通。我猜默认是创建和更新,所以我只是从用户模型中删除了它并且测试通过了。谢谢凯尔!
    【解决方案2】:

    您有用于 UsersController 更新操作的模板吗?

    它应该在app/view/users/update.html.erb

    附带说明,通常在成功更新时会重定向,因此如果您在更新操作中添加正确的redirect_to,您可能不需要该模板。

    【讨论】:

    • 我没有更新模板,但我认为本次测试不需要它。我还没有到测试成功编辑的地步。因此,基于用户控制器,它“应该”呈现编辑。或者至少我是这样解释代码的。
    • 该错误专门抱怨缺少该模板。是什么让您认为事实并非如此?
    • 假设测试失败是为了检查提交的无效数据。所以它不应该被定向到更新页面,它应该被重定向到编辑页面,因为它不应该通过身份验证。我同意错误具体是缺少模板,但是此测试不应该关心更新模板。至少现在还没有。
    【解决方案3】:

    下面的块

        describe "edit" do
          let(:user) { FactoryGirl.create(:user) }
          before { visit edit_user_path(user) }
    
          describe "page" do
            it { should have_selector('h1',    text: "Update your profile") }
            it { should have_selector('title', text: "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
        end
    

    创建一个@user,并且不更改表单中的任何内容,单击保存按钮,因此它会发送所有必需的字段内容,并在相应的控制器中作为成功更新处理。

    如果你改变了最后一个块

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

    那么 name 字段将为空,操作将作为不成功的更新处理并落入 else 块以呈现“编辑”。

    【讨论】:

      猜你喜欢
      • 1970-01-01
      • 2017-12-06
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      • 1970-01-01
      相关资源
      最近更新 更多