<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Click on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/click/</link>
    <description>Recent content in Click on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 31 Jul 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/click/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Python CLI Testing Libraries: Click Testing vs Typer Testing vs Argparse Tests for Reliable Command-Line Tools</title>
      <link>https://www.pistack.xyz/posts/2026-07-31-python-cli-testing-click-typer-argparse/</link>
      <pubDate>Fri, 31 Jul 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-07-31-python-cli-testing-click-typer-argparse/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Python&amp;rsquo;s command-line tool ecosystem is one of the richest in any programming language. Libraries like Click and Typer have made building beautiful CLIs effortless, while the standard library&amp;rsquo;s argparse remains a workhorse for simpler needs. But writing the CLI is only half the battle — testing it thoroughly is what separates reliable tools from fragile ones.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
