- xml - AJAX/Jquery XML 解析
- 具有多重继承的 XML 模式
- .net - 枚举序列化 Json 与 XML
- XML 简单类型、简单内容、复杂类型、复杂内容
我的 spec/controllers/decidings_controller_spec.rb 在下面。
RSpec.describe DecidingsController, type: :controller do
describe '#create' do
before do
@deciding=build(:deciding_consenting_false)
end
context 'correct_user login' do
before do
login_user(@deciding.asking.user)
end
it 'creates with deciding +1' do
expect{post :create , undertaking_id: @deciding.undertaking_id , asking_id: @deciding.asking_id}.to change(Deciding , :count).by(1)
end
it 'redirects to undertking' do
post :create , undertaking_id: @deciding.undertaking_id , asking_id: @deciding.asking_id
expect(response).to redirect_to @deciding.undertaking
end
end
context 'incorrect_user login' do
before do
@user=create(:user)
login_user(@user)
end
it 'creates with deciding 0' do
expect{post :create , undertaking_id: @deciding.undertaking_id , asking_id: @deciding.asking_id}.to change(Deciding , :count).by(0)
end
it 'redirects to undertking' do
post :create , undertaking_id: @deciding.undertaking_id , asking_id: @deciding.asking_id
expect(response).to redirect_to root_path
end
end
end
describe '#destroy' do
context 'before deciding consent' do
before do
@deciding=create(:deciding_consenting_false)
end
context 'correct_user login' do
before do
login_user(@deciding.asking.user)
end
it 'destroy with deciding -1' do
expect{delete :destroy , undertaking_id: @deciding , asking_id: @deciding}.to change(Deciding , :count).by(-1)
end
it 'redirects undertaking show' do
delete :destroy , undertaking_id: @deciding.undertaking_id , asking_id: @deciding.asking_id
expect(response).to redirect_to @deciding.undertaking
end
end
context 'incorrect_user login' do
before do
user=create(:user)
login_user(user)
end
it 'destroy with deciding -1' do
expect{delete :destroy , undertaking_id: @deciding , asking_id: @deciding}.to change(Deciding , :count).by(0)
end
it 'redirects undertaking show' do
delete :destroy , undertaking_id: @deciding.undertaking_id , asking_id: @deciding.asking_id
expect(response).to redirect_to root_path
end
end
end
context ' if after deciding consent( should #before_consent)' do
before do
@deciding=create(:deciding_consenting_true)
end
context 'correct_user login' do
before do
login_user(@deciding.asking.user)
end
it 'destroy with deciding 0' do
expect{delete :destroy , undertaking_id: @deciding , asking_id: @deciding}.to change(Deciding , :count).by(0)
end
it 'redirects undertaking show' do
delete :destroy , undertaking_id: @deciding.undertaking_id , asking_id: @deciding.asking_id
expect(response).to redirect_to root_path
end
end
end
end
describe '#consent' do
context 'correct_user login' do
before do
@deciding=create(:deciding_consenting_false)
login_user(@deciding.undertaking.user)
end
it 'consenting changes true' do
patch :consent , undertaking_id: @deciding.undertaking_id
@deciding.reload
expect(@deciding.consenting).to eq true
end
it 'redirect_to undertaking' do
patch :consent , undertaking_id: @deciding.undertaking_id
expect(response).to redirect_to @deciding.undertaking
end
end
context 'asking user login' do
before do
@deciding=create(:deciding_consenting_false)
login_user(@deciding.asking.user)
end
it 'consenting not changes true' do
patch :consent , undertaking_id: @deciding.undertaking_id
@deciding.reload
expect(@deciding.consenting).to eq false
end
it 'redirect_to root' do
patch :consent , undertaking_id: @deciding.undertaking_id
expect(response).to redirect_to root_path
end
end
context 'incorrect_user login' do
before do
@deciding=create(:deciding_consenting_false)
@user=create(:user)
login_user(@user)
end
it 'consenting not changes true' do
patch :consent , undertaking_id: @deciding.undertaking_id
@deciding.reload
expect(@deciding.consenting).to eq false
end
it 'redirect_to root' do
patch :consent , undertaking_id: @deciding.undertaking_id
expect(response).to redirect_to root_path
end
end
end
describe '#deciding_cancel' do
context 'correct_user login' do
context 'asking user login' do
context 'should #after_consent' do
before do
@deciding=create(:deciding_consenting_true)
login_user(@deciding.asking.user)
end
end
context 'should not before consent' do
before do
@deciding=create(:deciding_consenting_false)
login_user(@deciding.asking.user)
end
end
context 'should #before_finish' do
before do
@deciding=create(:deciding_consenting_true)
login_user(@deciding.asking.user)
end
end
context 'should not before finish' do
before do
@deciding=create(:deciding_after_finish)
login_user(@deciding.asking.user)
end
end
end
context 'undertaking user login' do
end
end
context 'incorrect_user login' do
before do
@user=create(:user)
end
end
end
describe '#deciding_cancel' do
context 'correct_user login' do
end
context 'incorrect_user login' do
end
end
describe '#deciding_cancel' do
context 'correct_user login' do
end
context 'incorrect_user login' do
end
end
结束
我的 Decidingscontroller 有很多用于条件分支的 before_action。所以我的规范文件变得太长了。在这种情况下还有其他方法吗?如果还有其他方法可以缩短程序,请告诉我。
无论如何,我的 controllers/decidings_controller.rb 在下面。
class DecidingsController < ApplicationController
#correct_user?
before_action :authenticate_user!
before_action :asking_user!, only: [:create , :destroy , :asking_finish , :finish_cancel ]
before_action :undertaking_user!, only: [:consent , :undertaking_finish]
before_action :asking_or_undertaking_user! , only: [:deciding_cancel,:deciding_cancel_consent , :deciding_cancel_refuse]
before_action :reverse_user! ,only: [:deciding_cancel_consent , :deciding_cancel_refuse]
#流れ
before_action :before_consent , only: [:destroy]
before_action :after_consent , only: [:deciding_cancel ,:deciding_cancel_consent , :deciding_cancel_refuse, :undertaking_finish , :asking_finish , :finish_cancel ]
before_action :before_finish , only: [:deciding_cancel ,:deciding_cancel_consent , :deciding_cancel_refuse]
before_action :after_deciding_cancel , only: [:deciding_cancel_consent , :deciding_cancel_refuse]
before_action :after_undertaking_finish , only: [:asking_finish , :finish_cancel]
def create
asking=Asking.find(params[:asking_id])
undertaking=Undertaking.find(params[:undertaking_id])
deciding=Deciding.new(asking_id: asking.id , undertaking_id: undertaking.id)
if deciding.save
flash[:success] = "契約作成に成功しました。"
redirect_to undertaking
else
flash[:alert] = "契約作成に失敗しました。"
redirect_to undertaking
end
end
def destroy
asking=Asking.find(params[:asking_id])
undertaking=Undertaking.find(params[:undertaking_id])
asking.deciding.destroy
flash[:info]='契約申し込みをキャンセルしました。'
redirect_to undertaking
end
def consent
undertaking=Undertaking.find(params[:undertaking_id])
if undertaking.deciding
undertaking.deciding.update(consenting: true)
flash[:success] = "契約が成立しました。"
redirect_to undertaking
else
redirect_to root_path
end
end
def deciding_cancel
undertaking=Undertaking.find(params[:undertaking_id])
undertaking.deciding.update(cancel: true , cancel_userid: current_user.id)
flash[:success] = "途中終了リクエストを送信しました。"
redirect_to undertaking
end
def deciding_cancel_consent
undertaking=Undertaking.find(params[:undertaking_id])
undertaking.deciding.destroy
flash[:success] = "契約が途中終了されました。"
redirect_to undertaking
end
def deciding_cancel_refuse
undertaking=Undertaking.find(params[:undertaking_id])
undertaking.deciding.update(cansel: false , cansel_userid: nil)
flash[:success] = "契約の途中終了を却下しました。"
redirect_to undertaking
end
def undertaking_finish
undertaking=Undertaking.find(params[:undertaking_id])
undertaking.deciding.update(finish_undertaking: true)
flash[:success] = "納品が完了しました。"
redirect_to undertaking
end
def finish_cancel
undertaking=Undertaking.find(params[:undertaking_id])
undertaking.deciding.update(finish_undertaking: false)
flash[:success] = "再納品リクエストを送信しました。"
redirect_to undertaking
end
def asking_finish
undertaking=Undertaking.find(params[:undertaking_id])
undertaking.deciding.update(finish_asking: true)
flash[:success] = "納品が成立しました。"
redirect_to asking
end
private
def asking_user!
asking=Asking.find(params[:asking_id])
unless asking.user==current_user
redirect_to root_path
end
end
def undertaking_user!
undertaking=Undertaking.find(params[:undertaking_id])
unless undertaking.user==current_user
redirect_to root_path
end
end
def asking_or_undertaking_user!
undertaking=Undertaking.find(params[:undertaking_id])
unless current_user==undertaking.user || current_user==undertaking.asking.user
refirect_to root_path
end
end
def reverse_user!
undertaking=Undertaking.find(params[:undertaking_id])
if current_user.id == undertaking.deciding.cansel_userid
refirect_to root_path
end
end
def before_consent
undertaking=Undertaking.find(params[:undertaking_id])
if undertaking.deciding.consenting
redirect_to root_path
end
end
def after_consent
asking=Asking.find(params[:asking_id])
unless asking.deciding.consenting
redirect_to root_path
end
end
def before_finish
undertaking=Undertaking.find(params[:undertaking_id])
if undertaking.deciding.finish_undertaking
redirect_to root_path
end
end
def after_deciding_cancel
undertaking=Undertaking.find(params[:undertaking_id])
unless undertaking.deciding.cancel
redirect_to root_path
end
end
def after_undertaking_finish
undertaking=Undertaking.find(params[:undertaking_id])
unless undertaking.deciding.finish_undertaking
redirect_to root_path
end
end
结束
请帮帮我...
最佳答案
我不会担心 Rails 中的长 Controller 和规范文件。
这些文件往往会变得很长,保持类和方法简短的通常建议不一定适用于 Controller 及其规范。
比如我们生产系统中的user_controller.rb
是8500行,对应的user_controller_spec.rb
是7000行。
这是我们排名前 10 的 Controller 的长度
1285 app/controllers/*********_controller.rb
1430 app/controllers/***********_controller.rb
1444 app/controllers/****_controller.rb
1950 app/controllers/****_controller.rb
1994 app/controllers/********_controller.rb
2530 app/controllers/***********_controller.rb
2697 app/controllers/*********_controller.rb
2998 app/controllers/*****_controller.rb
3134 app/controllers/application_controller.rb
8737 app/controllers/users_controller.rb
关于ruby-on-rails - Rspec Controller 测试通常是否太长?,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/41354277/
在我们的服务出现一些预期的增长之后,突然间一些更新花费了非常长的时间,这些过去非常快,直到表达到大约 2MM 记录,现在它们每个需要大约 40-60 秒。 update table1 set fiel
我在服务中实现了一个传感器事件监听器,只要采样周期和最大报告延迟低于 1 秒,该监听器就可以正常工作,但一旦我将采样周期增加到超过 1 秒,传感器就根本不会更新。 我希望采样周期为 10 秒(可能是
我使用 Tkinter GUI 来启动测量和分析过程,基本上只需单击一个按钮即可开始。由于这些测量可能需要一段时间,我尝试添加一个进度条,即这个: http://tkinter.unpythonic.
我正在尝试使用套接字发送数据包,但出现错误。 invalid conversion from ‘omnetpp::cPacket*’ to ‘inet::Packet*’ [-fpermissive]
我刚刚发现 String#split 有以下奇怪的行为: "a\tb c\nd".split => ["a", "b", "c", "d"] "a\tb c\nd".split(' ') => ["a
您好,我正在尝试 ClojureScript,我正在使用 Klipse作为我的 REPL 差不多。这可能不是它的预期用途,但因为我没有做任何太复杂的事情,所以现在没问题。 我遇到的一个问题是尝试设置计
根据下面的数据,ClockKit 会生成一次 future 的 CLKComplicationTimelineEntry 项,但对于过去的时间点,会进行 24 次调用!这是为什么? 更多详情: 我注意
我有一个 MySQL 表,这个表有一个名为 datetime_utc 的 DATETIME 列。如您所料,它是 UTC 日期和时间。在我的 Bookshelf 模型中,我定义了一个虚拟 getter,
大家好,我是二哥呀! 昨天,一位球友问我能不能给他解释一下 @SpringBootApplication 注解是什么意思,还有 Spring Boot 的运行原理,于是我就带着他扒拉了一下这个注解的源
我是一名优秀的程序员,十分优秀!