<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Checkcraft</title>
    <description>The latest articles on DEV Community by Checkcraft (@checkcraft).</description>
    <link>https://dev.to/checkcraft</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4256285%2Fb97d7dfd-75d4-4ea9-becf-74de0092ba09.png</url>
      <title>DEV Community: Checkcraft</title>
      <link>https://dev.to/checkcraft</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/checkcraft"/>
    <language>en</language>
    <item>
      <title>We built a practice API where every response is 200 OK and 10 bugs hide inside</title>
      <dc:creator>Checkcraft</dc:creator>
      <pubDate>Fri, 20 Nov 2026 19:33:20 +0000</pubDate>
      <link>https://dev.to/checkcraft/we-built-a-practice-api-where-every-response-is-200-ok-and-10-bugs-hide-inside-1cc1</link>
      <guid>https://dev.to/checkcraft/we-built-a-practice-api-where-every-response-is-200-ok-and-10-bugs-hide-inside-1cc1</guid>
      <description>&lt;p&gt;Disclosure first: this post is from the Checkcraft team (we make an API-checking desktop app), and the practice API below lives on our site. It is free, needs no sign-up and doesn't require our app. Postman, curl or the browser are enough.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why another practice API?
&lt;/h2&gt;

&lt;p&gt;JSONPlaceholder, Reqres and Restful-Booker are great for learning how to &lt;em&gt;send&lt;/em&gt; requests. But they behave correctly, so they never teach the habit that matters most in API testing: &lt;strong&gt;a 200 status tells you the server understood you, not that the result is right.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;So we made a small online-shop API where everything returns 200 and ten bugs are planted in the data.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try one
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight http"&gt;&lt;code&gt;&lt;span class="no"&gt;GET&lt;/span&gt; &lt;span class="n"&gt;https&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt;&lt;span class="c1"&gt;//checkcraft.ru/practice-api/v1/orders/5001.json&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;





&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="nl"&gt;"subtotal"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;3170.00&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="nl"&gt;"discount"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;300.00&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
&lt;span class="nl"&gt;"total"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="mf"&gt;2970.00&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;A typical test asserts &lt;code&gt;status == 200&lt;/code&gt; and &lt;code&gt;total &amp;gt; 0&lt;/code&gt;. Green. But 3170 − 300 = 2870: the customer was overcharged by 100.&lt;/p&gt;

&lt;p&gt;The other nine bugs are left for you. They are the kinds we keep meeting in real projects: a number sent as a string, a typo in a status, an extra field holding a secret, a list and a card that disagree, an answer that contradicts the log.&lt;/p&gt;

&lt;h2&gt;
  
  
  How to play
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Open the docs: &lt;a href="https://checkcraft.ru/en/guides/api-testing-practice.html?utm_source=devto" rel="noopener noreferrer"&gt;https://checkcraft.ru/en/guides/api-testing-practice.html?utm_source=devto&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Send requests from the page, Postman or curl.&lt;/li&gt;
&lt;li&gt;When you spot a mismatch, pick the response, type the field and press Check: the page tells you if you found a planted bug.&lt;/li&gt;
&lt;/ol&gt;

&lt;h2&gt;
  
  
  The lesson for automated tests
&lt;/h2&gt;

&lt;p&gt;If your test only checks the status and that fields exist, it would pass on all ten bugs. Check relationships instead: total = subtotal − discount, status agrees with paidAt, the order in the response matches the record in the log (&lt;code&gt;/practice-api/logs/orders-service.txt&lt;/code&gt;). Whatever tool you use, feed your test a deliberately wrong response once. If it stays green, it checks nothing.&lt;/p&gt;

&lt;p&gt;Found a bug we didn't plant? Tell us in the comments.&lt;/p&gt;

</description>
      <category>testing</category>
      <category>api</category>
      <category>beginners</category>
      <category>qa</category>
    </item>
  </channel>
</rss>
