Question

我的规格将通过master分支。如果我创建一个新分支并修改一些与订阅完全无关的代码，它们将失败。我可以让他们通过的唯一方法是将我的vcr.rb更改为:record => :new_episodes。

如果我保留该选项，那么几乎每次我的规格运行时，我都会有新的修改后的数据文件，这些文件最终会被提交，这真的会稀释Git的日志。

有关如何处理此问题的任何建议？许多破坏的规格都基于这个匹配器：

  describe "#change_plan_to", vcr: {match_requests_on: [:method, :uri, :body]} do

这个匹配器是否对变化过于开放？我无法通过条带api调用获得规范通过任何其他方式。

Failure/Error: @subscription.create_stripe_customer
     VCR::Errors::UnhandledHTTPRequestError:


       ================================================================================
       An HTTP request has been made that VCR does not know how to handle:
         POST https://api.stripe.com/v1/customers

       VCR is currently using the following cassette:
         - /Users/app/spec/data/Subscription/_change_plan_to/stripe_customer_subscription_plan_/name/.json
         - :record => :once
         - :match_requests_on => [:method, :uri, :body]

       Under the current configuration VCR can not find a suitable HTTP interaction
       to replay and is prevented from recording new requests. There are a few ways
       you can deal with this:

         * If you're surprised VCR is raising this error
           and want insight about how VCR attempted to handle the request,
           you can use the debug_logger configuration option to log more details [1].
         * You can use the :new_episodes record mode to allow VCR to
           record this new request to the existing cassette [2].
         * If you want VCR to ignore this request (and others like it), you can
           set an `ignore_request` callback [3].
         * The current record mode (:once) does not allow new requests to be recorded
           to a previously recorded cassette. You can delete the cassette file and re-run
           your tests to allow the cassette to be recorded with this request [4].
         * The cassette contains 109 HTTP interactions that have not been
           played back. If your request is non-deterministic, you may need to
           change your :match_requests_on cassette option to be more lenient
           or use a custom request matcher to allow it to match [5].

       [1] https://www.relishapp.com/vcr/vcr/v/2-5-0/docs/configuration/debug-logging
       [2] https://www.relishapp.com/vcr/vcr/v/2-5-0/docs/record-modes/new-episodes
       [3] https://www.relishapp.com/vcr/vcr/v/2-5-0/docs/configuration/ignore-request
       [4] https://www.relishapp.com/vcr/vcr/v/2-5-0/docs/record-modes/once
       [5] https://www.relishapp.com/vcr/vcr/v/2-5-0/docs/request-matching
       ================================================================================
     # ./app/models/subscription.rb:83:in `create_stripe_customer'
     # ./spec/models/subscription_spec.rb:68:in `block (3 levels) in <top (required)>'
     # -e:1:in `<main>'

我想出了更多。当我向堆栈添加新规范时，规范才会中断。当更多的东西被添加到套件中时，他们怎么破坏？

Answer 1

您看到的行为表明，用于匹配请求的其中一个属性是非确定性的，并且每次运行测试时都会更改。你提到使用match_requests_on: [:method, :uri, :body]选项 - 我猜它是body。请记住，VCR的内置物体匹配器会进行直接body_string == body_string比较，并且很容易出现这样的情况，即物体在语义上是等效的，但不是相同的字符串。例如，一个JSON字符串，如{"a": 1", "b": 2} vs {"b": 2, "a": 1}。

我的建议是在body上根本不匹配：如果你在某些情况下需要它，它就在那里，但如果你更宽松地匹配，VCR通常工作正常，因为它按照他们的顺序记录HTTP交互最初发生，然后，在播放过程中，它播放第一个未使用的匹配交互 - 如果您的测试按照原来的顺序进行请求，将导致为每个请求播放正确的响应。

为了更准确地了解正在发生的事情，您可以使用debug logger选项，它会在尝试匹配时为您提供详细的输出，以显示它正在执行的操作。

VCR未处理http请求错误

1 个答案: