如何在应用程序控制器中测试方法？我的方法使其他测试随机崩溃

debugcn 发表于 Dev

约书亚·穆海姆（Joshua Muheim）

我在应用程序控制器中有一个简单的方法：

class ApplicationController < ActionController::Base
  def filename_for_export(project, type, format = nil)
    buffer = "#{project.customer} - #{project.name} (#{type}, #{t 'org.name'}, #{Date.today.to_s :db})"
    buffer += ".#{format}" if format
    buffer
  end
end

我对此进行以下测试：

describe ApplicationController do
  describe '#filename_for_export' do
    before { @controller = ApplicationController.new }

    it 'returns a good human readable filename' do
      project = create(:project)
      result = @controller.instance_eval{ filename_for_export(project, 'Audit') }
      expect(result).to eq 'Project test customer - Project test name (Audit, Access for all, 2015-06-15)'
    end
  end
end

一切正常。然后我添加了另一个测试：

it 'appends a format extension if given' do
  project = create(:project)
  result = @controller.instance_eval{ filename_for_export(project, 'Audit', 'pdf') }
  expect(result).to eq 'Project test customer - Project test name (Audit, Access for all, 2015-06-15).pdf'
end

也工作正常。但有趣的是，此第二次测试似乎破坏了某些使其他许多规格随机失效的条件：

...
rspec ./spec/features/file_upload_spec.rb:18 # File upload displays a preview of an uploaded file
rspec ./spec/features/file_upload_spec.rb:4 # File upload allows to upload a file
rspec ./spec/features/file_upload_spec.rb:27 # File upload displays a preview of an uploaded file (from the temporary cache) after a re-display of the form
rspec ./spec/features/file_upload_spec.rb:60 # File upload allows to remove a file
rspec ./spec/features/markdown_spec.rb:4 # Markdown uses Pandoc as converter for inline markdown
rspec ./spec/features/users/destroy_spec.rb:22 # Deleting user signed in as admin grants permission to delete other user
rspec ./spec/features/success_criteria/show_spec.rb:6 # Showing success criterion displays a success criterion
rspec ./spec/features/boilerplate_originals/edit_spec.rb:11 # Editing boilerplate grants permission to edit a boilerplate
...

它始终是另一组失败的规范（我想这是一些订单问题），但是我不知道会破坏什么？第二个规范与第一个规范没有任何不同，那么它会破坏什么呢？

扬·布西克（Jan Bussieck）

如果你必须这样做，你可以使用Rspec的的匿名控制器描述在这里

 ...

 controller do
   def index
     project = create(:project)
     render json: filename_for_export(project, 'Audit', 'pdf')
   end
 end

 it 'appends a format extension if given' do
   get :index
   expect(JSON.parse(response.body)).to eq 'Project test customer - Project test name (Audit, Access for all, 2015-06-15).pdf'
 end

但是，我强烈建议您仅将此方法提取到一个普通的旧红宝石对象中，并作为单元测试对其进行隔离测试。您为“常规”控制器方法编写的请求规范应涵盖集成。

本文收集自互联网，转载请注明来源。

如有侵权，请联系[email protected] 删除。