<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CI/CD on API Coding</title>
    <link>https://apicoding.com/tags/ci/cd/</link>
    <description>Recent content in CI/CD on API Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 05 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://apicoding.com/tags/ci/cd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Record an Agent&#39;s MCP Traffic Once, Then Replay It in CI Without Servers or Credentials</title>
      <link>https://apicoding.com/record-an-agents-mcp-traffic-once-then-replay-it-in-ci-without-servers-or-credentials/</link>
      <pubDate>Mon, 05 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://apicoding.com/record-an-agents-mcp-traffic-once-then-replay-it-in-ci-without-servers-or-credentials/</guid>
      <description>&lt;p&gt;Your agent test passes on your laptop and fails in CI. The laptop has a token for the issue tracker&amp;rsquo;s MCP server; CI doesn&amp;rsquo;t, and shouldn&amp;rsquo;t. Even with a token, the tracker listed three open bugs yesterday and lists four today, so the agent&amp;rsquo;s summary changes and the assertion on it breaks.&lt;/p&gt;&#xA;&lt;p&gt;Web developers dealt with this years ago. VCR (Ruby), Polly.js, Betamax and go-vcr record real HTTP responses into a file the first time a test runs, then serve them from that file on every run after. The file is called a cassette. MCP needs the same thing: a proxy that sits between an agent and its MCP servers, writes every exchange into one cassette, and plays it back later with no server, no credentials and no network. &lt;code&gt;mcprec&lt;/code&gt; below is an illustrative name for a tool you&amp;rsquo;d have to build.&lt;/p&gt;</description>
    </item>
    <item>
      <title>API Testing Strategies: What to Test and When</title>
      <link>https://apicoding.com/api-testing-strategies-what-to-test-and-when/</link>
      <pubDate>Thu, 17 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://apicoding.com/api-testing-strategies-what-to-test-and-when/</guid>
      <description>&lt;p&gt;An API can pass every unit test in its suite and still break every client that calls it, because unit tests check that functions do what the code says they do, not that the API does what the contract says it does. That gap is where most production API incidents actually come from: a field renamed, a status code changed from 200 to 204, a required parameter quietly made optional. Testing an API well means testing at several different levels, because each one catches a different class of failure.&lt;/p&gt;</description>
    </item>
    <item>
      <title>API Testing Strategies That Catch the Problems Unit Tests Miss</title>
      <link>https://apicoding.com/api-testing-strategies-that-catch-the-problems-unit-tests-miss/</link>
      <pubDate>Mon, 09 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://apicoding.com/api-testing-strategies-that-catch-the-problems-unit-tests-miss/</guid>
      <description>&lt;p&gt;Unit tests verify that individual functions behave correctly in isolation. They run fast, catch regressions close to where they are introduced, and document expected behavior at the code level. They do not verify that the API endpoints exposed to consumers behave according to the documented contract, that changes in one service do not break the consumers that depend on it, or that the system behaves correctly under the conditions that production traffic creates.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
