<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hi Dan,</p>
    <p>Thanks, that's really interesting.</p>
    <p>I guess that was a custom setup, rather than something you could
      just turn on as part of the VCR config?</p>
    <p>I think something like this could be the basis of a VCRbot that
      put in PRs with some frequency ...<br>
    </p>
    <p>Many thanks</p>
    <p>Best, Sam<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 11/09/2018 11:06, Dan Lucraft wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CADwsFP_Lyk23=S=zDfhiZ5GX17GFmTgHKDMWzBTgyk6FhYVppA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=utf-8">
      <div dir="ltr">I've used VCR in the past, and the way it worked
        was our test suite had an optional "live" mode, which ran the
        tests against the live APIs.
        <div><br>
        </div>
        <div>This meant a lot more up-front work, in that the tests had
          to be able to work from VCR stubs AND also be able to do all
          the real setup work in a live api, but it was very useful.</div>
        <div><br>
        </div>
        <div>Every so often we'd run it in live mode, and if the APIs
          had then changed the VCR stubs would be updated on disc and
          inspectable before checking them in for changes.</div>
        <div><br>
        </div>
        <div><br>
        </div>
      </div>
      <div class="gmail_extra"><br clear="all">
        <div>
          <div class="gmail_signature" data-smartmail="gmail_signature">
            <div dir="ltr">
              <div>
                <div dir="ltr">
                  <div dir="ltr">
                    <table
                      style="font-size:12.8px;font-family:times;border-collapse:collapse">
                      <tbody>
                        <tr>
                          <td style="vertical-align:top"><a
href="https://www.charliehr.com/?utm_source=tom&utm_medium=email&utm_campaign=signature"
                              style="color:rgb(17,85,204)"
                              target="_blank" moz-do-not-send="true"><img
src="https://s3-eu-west-1.amazonaws.com/charlie-production/static/email-signature-icon.png"
                                alt="Charlie Logo"
                                style="width:50px;margin-right:10px"
                                moz-do-not-send="true"></a></td>
                          <td>
                            <h2
style="margin:0px;color:rgb(46,66,77);font-family:helvetica,arial,sans-serif;font-weight:normal;line-height:1.2em;font-size:18px">Dan
                              Lucraft</h2>
                            <p style="margin:0px 0px
2px;font-family:helvetica,arial,sans-serif;color:rgb(95,110,138);line-height:1.2em;font-size:13px">Head
                              of Engineering</p>
                            <p
style="margin:0px;font-family:helvetica,arial,sans-serif;color:rgb(95,110,138);line-height:1.2em;font-size:13px">CharlieHR</p>
                          </td>
                        </tr>
                      </tbody>
                    </table>
                    <br>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
        <br>
        <div class="gmail_quote">On 11 September 2018 at 10:07, Samuel
          Joseph <span dir="ltr"><<a href="mailto:tansaku@gmail.com"
              target="_blank" moz-do-not-send="true">tansaku@gmail.com</a>></span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi
            Lrugers,<br>
            <br>
            Any thoughts on how to manage VCR caches effectively in a
            team context?<br>
            <br>
            <a href="https://github.com/vcr/vcr" rel="noreferrer"
              target="_blank" moz-do-not-send="true">https://github.com/vcr/vcr</a><br>
            <br>
            We have a few open source projects using VCR, and we have
            the recordings of the network communication checked into git
            so that all developers can run tests in a consistent network
            environment.<br>
            <br>
            I have two concerns<br>
            <br>
            1) new developers onboarding often get snarled up in the
            caching and the files generated<br>
            2) the cached recordings are gradually getting further and
            further out of date - could we automate their refreshing?<br>
            <br>
            I have reached out to the VCR community in the past, but
            haven't had much feedback:<br>
            <br>
            * <a href="https://github.com/vcr/vcr/issues/672"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/vcr/vcr/iss<wbr>ues/672</a><br>
            * <a href="https://github.com/vcr/vcr/issues/719"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://github.com/vcr/vcr/iss<wbr>ues/719</a><br>
            * <a
              href="https://groups.google.com/forum/#%21topic/vcr-ruby/8DoA7MUq-38"
              rel="noreferrer" target="_blank" moz-do-not-send="true">https://groups.google.com/foru<wbr>m/#!topic/vcr-ruby/8DoA7MUq-38</a><br>
            <br>
            I wondered if anyone else was using VCR and how they were
            making it work well for them with their team.  Perhaps
            people are not using it and doing something else?<br>
            <br>
            Many thanks in advance<br>
            <br>
            Best, Sam<br>
            <br>
            ______________________________<wbr>_________________<br>
            Chat mailing list<br>
            <a href="mailto:Chat@lists.lrug.org" target="_blank"
              moz-do-not-send="true">Chat@lists.lrug.org</a><br>
            Archives: <a
              href="http://lists.lrug.org/pipermail/chat-lrug.org"
              rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.lrug.org/pipermai<wbr>l/chat-lrug.org</a><br>
            Manage your subscription: <a
              href="http://lists.lrug.org/options.cgi/chat-lrug.org"
              rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.lrug.org/options.<wbr>cgi/chat-lrug.org</a><br>
            List info: <a
              href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org"
              rel="noreferrer" target="_blank" moz-do-not-send="true">http://lists.lrug.org/listinfo<wbr>.cgi/chat-lrug.org</a><br>
          </blockquote>
        </div>
        <br>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Chat mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a>
Archives: <a class="moz-txt-link-freetext" href="http://lists.lrug.org/pipermail/chat-lrug.org">http://lists.lrug.org/pipermail/chat-lrug.org</a>
Manage your subscription: <a class="moz-txt-link-freetext" href="http://lists.lrug.org/options.cgi/chat-lrug.org">http://lists.lrug.org/options.cgi/chat-lrug.org</a>
List info: <a class="moz-txt-link-freetext" href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>