Rspec.测试后自动启动测试代码



我在测试Sensu插件时遇到了问题。每次当我启动rspec测试插件时,它都会测试它,但无论如何,在测试结束时,原始插件会自动启动。所以我在控制台输入:

Finished in 0 seconds (files took 0.1513 seconds to load) 
1 example, 0 failures 
CheckDisk OK:       # This comes from the plugin

我的系统如何工作的简短解释:插件调用系统'wmic'命令,处理它,检查磁盘参数的条件并返回退出状态(ok, critical,等等)Rspec模拟来自系统的响应,并设置为插件的输入。当给出模拟输入时,rspec检查插件退出状态。

我的插件是这样的:

require 'rubygems' if RUBY_VERSION < '1.9.0'
require 'sensu-plugin/check/cli'
class CheckDisk < Sensu::Plugin::Check::CLI
  def initialize
    super
    @crit_fs = []
  end
  def get_wmic
    `wmic volume where DriveType=3 list brief`
  end
  def read_wmic
    get_wmic
    # do something, fill the class variables with system response  
  end
  def run
   severity = "ok"
   msg = ""
   read_wmic
   unless @crit_fs.empty?
     severity = "critical"  
  end  
  case severity
    when /ok/
      ok msg
    when /warning/
      warning msg
    when /critical/
      critical msg
    end
  end
end

下面是我在Rspec中的测试:

require_relative '../check-disk.rb'
require 'rspec'
  def loadFile
    #Load template of system output when ask 'wmic volume(...)
  end
  def fillParametersInTemplate (template, parameters)
    #set mocked disk parameters in template
  end
  def initializeMocks (options)
    mockedSysOutput = fillParametersInTemplate @loadedTemplate, options 
    po = String.new(mockedSysOutput)
    allow(checker).to receive(:get_wmic).and_return(po) #mock system call here
  end
  describe CheckDisk do
    let(:checker) { described_class.new }
    before(:each) do   
       @loadedTemplate = loadFile   
       def checker.critical(*_args)
          exit 2
       end    
     end
  context "When % of free disk space = 10 >" do 
    options = {:diskName => 'C:\', :diskSize => 1000, :diskFreeSpace => 100}       
    it 'Returns ok exit status ' do      
      begin                   
        initializeMocks options
        checker.run 
      rescue SystemExit => e 
        exit_code = e.status   
      end 
      expect(exit_code).to eq 0
    end  
  end 
end

我知道我可以在最后一个例子后面放"exit 0",但这不是一个解决方案,因为当我尝试启动许多规范文件时,它将在第一个文件之后退出。如何开始只测试,而不运行插件?也许有人可以帮助我,告诉我如何处理这样的问题?谢谢你。

您可以存根原始插件调用,并可选择返回一个虚拟对象:

allow(SomeObject).to receive(:method) # .and_return(double)

你可以把它放在before块,以确保所有断言将共享代码。

另一件事是,您正在使用rescue块来捕获代码因错误而终止的情况。你应该使用raise_error匹配器代替:

expect { run }.to raise_error(SystemExit)

最新更新