<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Optic on Yunier&#39;s Wiki</title>
    <link>http://localhost:1313/tags/optic/</link>
    <description>Recent content in Optic on Yunier&#39;s Wiki</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Mon, 17 Apr 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="http://localhost:1313/tags/optic/rss" rel="self" type="application/rss+xml" />
    <item>
      <title>Tracking API Changes With Optic</title>
      <link>http://localhost:1313/post/2023/optic/</link>
      <pubDate>Mon, 17 Apr 2023 00:00:00 +0000</pubDate>
      <guid>http://localhost:1313/post/2023/optic/</guid>
      <description>&lt;p&gt;Over the last few months, I have been brushing up on &lt;a href=&#34;https://www.postman.com/api-platform/api-testing/&#34;&gt;API testing&lt;/a&gt;, specifically around contract testing.&lt;/p&gt;&#xA;&lt;p&gt;According to Postman, an API contract is a human- and machine-readable representation of an API&amp;rsquo;s intended functionality. It establishes a single source of truth for what each request and response should look like—and forms the basis of service-level agreements (SLAs) between producers and consumers. API contract testing helps ensure that new releases don&amp;rsquo;t violate the contract by checking the content and format of requests and responses.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
