<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Testing on Spaghetti Code 🍝</title>
    <link>https://spaghetti-code.net/en/tags/testing/</link>
    <description>Recent content in Testing on Spaghetti Code 🍝</description>
    <image>
      <title>Spaghetti Code 🍝</title>
      <url>https://spaghetti-code.net/images/og-default.png</url>
      <link>https://spaghetti-code.net/images/og-default.png</link>
    </image>
    <generator>Hugo -- 0.160.0</generator>
    <language>en</language>
    <lastBuildDate>Mon, 02 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://spaghetti-code.net/en/tags/testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Mocks vs Stubs vs Fakes vs Spies: Test Doubles Explained</title>
      <link>https://spaghetti-code.net/en/posts/testing/test-doubles-explained/</link>
      <pubDate>Mon, 02 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://spaghetti-code.net/en/posts/testing/test-doubles-explained/</guid>
      <description>Dummy, stub, spy, fake and mock: five test doubles that check different things. One Python class, tested all five ways, shows which to use in your next test.</description>
    </item>
    <item>
      <title>What Is TDD and How the Red-Green-Refactor Cycle Works</title>
      <link>https://spaghetti-code.net/en/posts/testing/what-is-tdd/</link>
      <pubDate>Sun, 18 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://spaghetti-code.net/en/posts/testing/what-is-tdd/</guid>
      <description>Test-driven development means writing a failing test before the code, making it pass, then cleaning up. The red-green-refactor cycle, with a full Python kata.</description>
    </item>
    <item>
      <title>Unit vs Integration vs End-to-End Tests Explained</title>
      <link>https://spaghetti-code.net/en/posts/testing/unit-vs-integration-vs-end-to-end-tests/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://spaghetti-code.net/en/posts/testing/unit-vs-integration-vs-end-to-end-tests/</guid>
      <description>Unit, integration, and end-to-end tests catch different bugs. One Flask sign-up tested at all three levels, with mocks vs fakes and why e2e tests go flaky.</description>
    </item>
  </channel>
</rss>
