Ruby on rails Rspec测试惨败
因此,我在这里看到了一些与我类似的问题,但距离不够近,无法帮助我找出我的问题所在……因此,任何关于我做错了什么的帮助都将不胜感激:(我正在关注Michael Hartl的教程,因此关于我如何偏离其示例的信息将特别有用)…thx 我的规格/功能/用户\u页面\u spec.rbRuby on rails Rspec测试惨败,ruby-on-rails,rspec,tdd,railstutorial.org,Ruby On Rails,Rspec,Tdd,Railstutorial.org,因此,我在这里看到了一些与我类似的问题,但距离不够近,无法帮助我找出我的问题所在……因此,任何关于我做错了什么的帮助都将不胜感激:(我正在关注Michael Hartl的教程,因此关于我如何偏离其示例的信息将特别有用)…thx 我的规格/功能/用户\u页面\u spec.rb require 'spec_helper' describe "Authentication" do subject { page } # FOR STATIC SIGN IN PAGE describe
require 'spec_helper'
describe "Authentication" do
subject { page }
# FOR STATIC SIGN IN PAGE
describe "signin page" do
before { visit signin_path }
it { should have_selector('h1', text: 'Sign in') }
it { should have_title('Sign in') }
end
# FOR SIGNIN PROCESS
describe "signin" do
before { visit signin_path }
describe "with invalid information" do
before { click_button "Sign in" }
it { should have_title('Sign in') }
it { should have_error_message }
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_title(user.name) }
it { should have_link('Profile', href: user_path(user)) }
it { should have_link('Sign out', href: signout_path) }
it { should have_link('Settings', href: edit_user_path(user)) }
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
# FOR AUTHORIZING WHICH ACCOUNTS CAN DO WHAT
describe "authorization" do
describe "for non-signed-in users" do
let(:user) { FactoryGirl.create(:user) }
describe "in the Users controller" do
describe "visiting the edit page" do
before { visit edit_user_path(user) }
it { should have_title('Sign in') }
end
describe "submitting to the update action" do
before { put user_path(user) }
specify { response.should redirect_to(signin_path) }
end
end
end
describe "as wrong user" do
let(:user) { FactoryGirl.create(:user) }
let(:wrong_user) { FactoryGirl.create(:user, email: "wrong@example.com") }
before { sign_in user }
describe "visiting Users#edit page" do
before { visit edit_user_path(wrong_user) }
it { should_not have_selector('title', text: full_title('Edit user')) }
end
describe "submitting a PUT request to the Users#update action" do
before { put user_path(wrong_user) }
specify { response.should redirect_to(root_path) }
end
end
end
end
require 'spec_helper'
describe "User pages" do
subject { page }
# TESTING STATIC PROFILE PAGE
describe "profile page" do
let(:user) { FactoryGirl.create(:user) } # Code to make a user variable
before { visit user_path(user) }
it { should have_selector('h1', text: user.name) }
it { should have_title(user.name) }
end
# TESTING STATIC SIGNUP PAGE
describe "signup page" do
before { visit signup_path }
it { should have_selector('h1', text: 'Sign up') }
it { should have_title("Sign up") }
end
# TESTING SIGN UP PROCESS
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_title('Sign up') }
it { should have_content('error') }
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_title(user.name) }
it { should have_selector('div.alert.alert-success', text: 'Welcome') }
it { should have_link('Sign out') }
end
end
end
# TESTING EDITING FUNCTIONALITY
describe "edit" do
let(:user) { FactoryGirl.create(:user) }
before do
sign_in user
visit edit_user_path(user)
end
describe "page" do
it { should have_selector('h1', text: "Update your profile") }
it { should have_title("Edit user") }
# it { should have_link('change', href: 'http://gravatar.com/emails') }
# needed if using gravatar
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 { user.reload.name.should == new_name }
specify { user.reload.email.should == new_email }
end
end
end
我的规范/support/utilities.rb
include ApplicationHelper
RSpec::Matchers.define :have_error_message do |message|
match do |page|
page.has_selector?('div.alert.alert-error', text: 'Invalid')
end
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.
# cookies[:remember_token] = user.remember_token
end
我的控制器/用户\u controller.rb
class UsersController < ApplicationController
before_filter :signed_in_user, only: [:edit, :update]
def new
@user = User.new
end
def show
@user = User.find(params[:id])
end
def create
@user = User.new(params[:user])
if @user.save
sign_in @user
flash[:success] = "Welcome to Authentication 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])
sign_in @user
flash[:success] = "Profile updated"
redirect_to @user
else
render 'edit'
end
end
def destroy
User.find(params[:id]).destroy
flash[:success] = "User destroyed"
redirect_to users_path
end
private
def signed_in_user
redirect_to signin_url, notice: "Please sign in." unless signed_in?
end
end
class UsersController
&最后,我的视图/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 %>
</div>
</div>
更新您的个人资料
任何和所有的帮助,以正确的修复将不胜感激。谢谢,
put、get、post、delete
,用于控制器测试的方法在功能测试中不可用
编写特性测试时,您应该通过按钮操作/ajax/等“提交”
put
,而不是像控制器测试那样发布到控制器。如果您正在学习Rails教程,则需要将您的Capybara版本降级到1.1.2,并将您的规范移动到spec/requests
目录中。更新您的文件:
gem 'capybara', '1.1.2'
如果您计划使用Capybara 2.0,我建议您阅读以下内容:
问题是:您将请求(
capybara
)测试与功能测试混为一谈
在capybara
中,您应该描述用户步骤
require 'spec_helper'
describe "Website access" do
context "when I am a registered user" do
it "should let me in" do
page.fill_in 'Email', with: 'vader@deathstar.com'
page.fill_in 'Password', with: 'mydearluke'
page.click_link 'Let me in'
page.should have_content('Welcome, cheif!')
end
end
context "when I am not a registered user" do
it "should not let me in" do
page.fill_in 'Email', with: 'jabba.h@tatooine.com'
page.fill_in 'Password', with: 'wormsarmageddon'
page.click_link 'Let me in'
page.should have_content('Incorrect credentials!')
end
end
end
功能测试在较低的级别上运行,因为您需要使用HTTP动词put
,get
,post
,delete
,与正在测试的应用程序进行通信
require 'spec_helper'
describe SessionsController do
context "when I am registered user" do
it "should let me in" do
post :create, email: 'vader@deathstar.com', password: 'mydearluke'
response.should be_success
end
end
context "when I am not a registered user" do
it "should not let me in" do
post :create, email: 'jabba.h@tatooine.com', password: 'wormsarmageddon'
response.should_not be_success
end
end
end
这里有几点需要注意:
post
,而不是put
descripe
块中指定控制器名称,这与capybara测试中的简单英语描述不同SessionController
应如何准确响应不同的用户凭据(它应为好用户创建会话,并对未注册的会话发出尖叫)访问并单击测试中的链接/单击按钮
put
,get
,post
,delete
)谢谢kwon-所以我应该把这些测试放到一个新的目录中。或者你能告诉我正确的方向吗?抱歉-对rspec和tdd来说还是很新的…也就是说,我可以完全删除描述“提交到更新操作”测试,但我认为这不是最好的主意…thxthanks人-看起来像是个讨厌鬼…所以基本上我必须回去,把所有不是水豚的测试放回规范/请求中???但是将水豚测试保存在/features文件夹中??(我坚持使用新的2+水豚-这个链接非常有用)如果你在学习Michael Hartl的教程,只需将文件从
spec/features
移动到spec/requests
。看看GitHub上的。如果其他任何人有问题/这些特定错误…我能够在这些人的帮助下得到答案…只需在spec/requests/文件夹中重新创建一个重复的身份验证\u pages\u spec.rb…去掉[descripe“submitting to the update action”do]测试,并将其放在新复制的文件中。(但别忘了也添加let(:user){FactoryGirl.create(:user)}看起来他仍然在使用旧版本的capybara…我刚刚在/features和/requests中得到了所有的capybara测试(这似乎起作用了——帖子中的错误至少在被扔进/request时起作用了——我很感激,伙计——这很有帮助(显然我没有足够的分数或东西来支持你的答案)
require 'spec_helper'
describe SessionsController do
context "when I am registered user" do
it "should let me in" do
post :create, email: 'vader@deathstar.com', password: 'mydearluke'
response.should be_success
end
end
context "when I am not a registered user" do
it "should not let me in" do
post :create, email: 'jabba.h@tatooine.com', password: 'wormsarmageddon'
response.should_not be_success
end
end
end