我使用的是Rspec 3.0和水豚2.4.3。我在spec/features/named challenge_users_spec.rb 中制作了一个功能规范
require "rails_helper"
feature "Challenge users" do
let!(:challenge) { create(:challenge)}
let(:user) { create(:user)}
context "as a registered user" do
before :each do
sign_in(user)
end
scenario "challenges himself" do
expect(current_path).to eq root_path
expect(page).to have_content challenge.name
click_button 'Accept'
expect(page).to have_content 'You accepted the challenge!'
expect(user.accepted_dares.count).to eq 1
end
scenario 'challenges other user' do
expect(current_path).to eq root_path
click_button 'Challenge others'
expect(current_path).to eq new_challenge_dare_path(challenge_id: challenge.id)
expect(page).to have_content 'Challenge with a bet!'
end
end
end
在第一个场景中,页面呈现正确的flash消息,但不更新用户。在第二个场景中,单击"挑战他人"后,current_path被设置为"/",而不是"挑战/:id/dales/new",因此没有达到最后两个预期。Dares模型是一个嵌套路由:
resources :challenges do
resources :dares
end
控制器方法大多是标准CRUD方法。
这是Rspec日志:
Failures:
1) Challenge users as a registered user challenges himself
Failure/Error: expect(user.accepted_dares.count).to eq 1
expected: 1
got: 0
(compared using ==)
# ./spec/features/challenge_users_spec.rb:18:in `block (3 levels) in <top (required)>'
2) Challenge users as a registered user challenges other user
Failure/Error: expect(current_path).to eq new_challenge_dare_path(challenge_id: challenge.id)
expected: "/challenges/2/dares/new"
got: "/"
(compared using ==)
# ./spec/features/challenge_users_spec.rb:26:in `block (3 levels) in <top (required)>'
Finished in 0.91199 seconds (files took 3.62 seconds to load)
2 examples, 2 failures
Failed examples:
rspec ./spec/features/challenge_users_spec.rb:10 # Challenge users as a registered user challenges himself
rspec ./spec/features/challenge_users_spec.rb:21 # Challenge users as a registered user challenges other user
型号:
Dare
class Dare < ActiveRecord::Base
belongs_to :challenge, counter_cache: true
belongs_to :acceptor, class_name: "User"
belongs_to :challenger, class_name: "User"
has_many :votes
before_save :change_status
before_save :create_start_date
before_save :set_proof_array
def set_proof_array
if self.utube_link.nil?
self.utube_link = []
save!
end
end
def create_start_date
if status == 'Accepted' && start_date.blank?
self.start_date = DateTime.now
end
end
def change_status
if status.blank?
if self.acceptor_id == self.challenger_id
self.status = "Accepted"
else
self.status = "Pending"
end
end
end
...
end
用户
class User < ActiveRecord::Base
# Include default devise modules. Others available are:
# :confirmable, :lockable, :timeoutable and :omniauthable
devise :database_authenticatable, :registerable,
:recoverable, :rememberable, :trackable, :validatable
has_many :dares, foreign_key: :challenger_id
has_many :accepted_dares, class_name: "Dare", foreign_key: :acceptor_id
has_many :challenges, through: :dares
has_many :votes
validates :username, presence: true, uniqueness: true, length: { in: 2..50 }
....
end
挑战
class Challenge < ActiveRecord::Base
has_many :dares
has_many :users, through: :dares, source: :challenges
validates :name, presence: true, uniqueness: true, length: { in: 5..100 }
validates :description, presence: true, length: { in: 10..500 }
include PgSearch
pg_search_scope :search, against: [:name, :description],
using: {tsearch: {prefix: true, dictionary: "english" }}
...
end
编辑
我没有提到这一点,但我在我的应用程序中使用了Turbolinks。在我的测试中添加js:true后,第二个测试通过了,但第一个测试仍然抛出了一个错误:
1) Challenge users as a registered user challenges himself
Failure/Error: expect(user.reload.accepted_dares.count).to eq 1
expected: 1
got: 0
(compared using ==)
这是两个不相关的问题。
用户模型不更新的原因是,它在内存中是一个完全独立的实例,与在后端更改的实例完全不同。您需要强制它从数据库中重新加载:
expect(user.reload.accepted_dares.count).to eq 1
current_path
没有为您提供期望值的原因是click_button
是一个异步操作。您对current_path
的断言将在单击按钮后立即执行,然后才有机会加载新页面。
Capybara的许多操作(如find
)会自动等待并重试,直到条件为真(在find
的情况下,它会等待选择器匹配页面上的某个内容),但由于current_path
没有任何条件,它会立即返回当前值(Capybara不知道在调用该方法时您期望的当前路径是什么)。
测试这一点的更好方法是查找一些内容,这些内容只会在单击按钮并重新加载页面后出现在页面上。这迫使Capybara在继续之前等待内容。
在这种情况下,颠倒两个断言的顺序就可以了:
expect(page).to have_content 'Challenge with a bet!'
expect(current_path).to eq new_challenge_dare_path(challenge_id: challenge.id)