如何用RSpec覆盖Ruby代码中所有Rescue代码块以获取测试覆盖率？

要覆盖代码里的三个rescue分支，核心思路是模拟ej.deliver_emails抛出对应层级的异常，同时mock所有依赖（避免真实执行的副作用），并断言异常处理逻辑的行为。以下是每个分支的具体测试方案：

1. 覆盖Timeout::Error分支 #

这个分支会捕获超时异常、记录错误日志并重新抛出异常，测试时需要验证这些行为：

it "处理Timeout::Error并重新抛出异常" do
  data = { key: "test_data" }
  agents = ["agent@example.com"]
  log_obj = double("LogObject")
  test_error = Timeout::Error.new("连接超时")

  # Mock依赖方法
  allow(described_class).to receive(:agent_emails).with(data).and_return(agents)
  allow(described_class).to receive(:log_obj).and_return(log_obj) # 根据实际情况调整log_obj的获取方式

  # 模拟EmailerJob的deliver_emails抛出超时异常
  emailer_job = double("EmailerJob")
  allow(EmailerJob).to receive(:new).with(agents: agents, data: data).and_return(emailer_job)
  allow(emailer_job).to receive(:deliver_emails).and_raise(test_error)

  # 断言日志调用
  expect(CommonLogger).to receive(:input_log).with(log_obj, "Sending Lead email to #{agents}")
  expect(CommonLogger).to receive(:input_log).with(log_obj, test_error.to_s, "error")

  # 断言异常被重新抛出
  expect { described_class.process_request(data) }.to raise_error(test_error)
end

2. 覆盖StandardError分支 #

这个分支处理除Timeout::Error外的标准异常，且不会重新抛出，测试时要选择不会被前一个分支捕获的StandardError子类（比如ArgumentError）：

it "处理StandardError且不重新抛出异常" do
  data = { key: "test_data" }
  agents = ["agent@example.com"]
  log_obj = double("LogObject")
  test_error = ArgumentError.new("无效的代理数据")

  # Mock依赖方法
  allow(described_class).to receive(:agent_emails).with(data).and_return(agents)
  allow(described_class).to receive(:log_obj).and_return(log_obj)

  # 模拟deliver_emails抛出StandardError子类
  emailer_job = double("EmailerJob")
  allow(EmailerJob).to receive(:new).with(agents: agents, data: data).and_return(emailer_job)
  allow(emailer_job).to receive(:deliver_emails).and_raise(test_error)

  # 断言日志和Rails.logger调用
  expect(CommonLogger).to receive(:input_log).with(log_obj, "Sending Lead email to #{agents}")
  expect(CommonLogger).to receive(:input_log).with(log_obj, test_error.to_s, "error")
  expect(Rails.logger).to receive(:error).with("StandardError Handling for #{agents}")

  # 断言方法执行后不抛出异常
  expect { described_class.process_request(data) }.not_to raise_error
end

3. 覆盖Exception分支 #

Exception是所有异常的父类，包含StandardError之外的异常（比如SystemExit），测试时需要用这类异常才能触发该分支：

it "处理Exception并重新抛出异常" do
  data = { key: "test_data" }
  agents = ["agent@example.com"]
  log_obj = double("LogObject")
  test_error = SystemExit.new(1)

  # Mock依赖方法
  allow(described_class).to receive(:agent_emails).with(data).and_return(agents)
  allow(described_class).to receive(:log_obj).and_return(log_obj)

  # 模拟deliver_emails抛出非StandardError的Exception子类
  emailer_job = double("EmailerJob")
  allow(EmailerJob).to receive(:new).with(agents: agents, data: data).and_return(emailer_job)
  allow(emailer_job).to receive(:deliver_emails).and_raise(test_error)

  # 断言日志和Rails.logger调用
  expect(CommonLogger).to receive(:input_log).with(log_obj, "Sending Lead email to #{agents}")
  expect(CommonLogger).to receive(:input_log).with(log_obj, test_error.to_s, "error")
  expect(Rails.logger).to receive(:error).with("Exception Handling for #{agents}")

  # 断言异常被重新抛出
  expect { described_class.process_request(data) }.to raise_error(test_error)
end

关键注意事项 #

• 确保log_obj的mock逻辑符合实际代码的获取方式（如果是参数传入，直接传入double即可）
• 异常捕获有顺序优先级，测试时要选择对应层级的异常，避免被前序rescue分支拦截
• 所有外部依赖（比如EmailerJob、CommonLogger）都要mock，避免测试依赖外部服务或产生副作用

内容的提问来源于stack exchange，提问作者Rashmi Balkur