<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Powershell on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/powershell/</link>
    <description>Recent content in Powershell on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 06 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/powershell/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Pester vs PSScriptAnalyzer vs PlatyPS: The PowerShell Module Toolchain in 2026</title>
      <link>https://www.pistack.xyz/posts/2026-09-06-powershell-module-testing-pester-psscriptanalyzer-platyps-comparison/</link>
      <pubDate>Sun, 06 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-06-powershell-module-testing-pester-psscriptanalyzer-platyps-comparison/</guid>
      <description>&lt;p&gt;Open the PowerShell Gallery and you will find thousands of modules that do one thing well and everything else badly: no tests, no style enforcement, and help files that consist of a single autogenerated stub. Meanwhile, the modules Microsoft itself ships go through a pipeline that most open-source projects never set up. That pipeline is built from three tools — &lt;strong&gt;Pester&lt;/strong&gt; (3,330 stars), &lt;strong&gt;PSScriptAnalyzer&lt;/strong&gt; (2,153 stars), and &lt;strong&gt;PlatyPS&lt;/strong&gt; (872 stars) — and together they turn &amp;ldquo;a script someone shared&amp;rdquo; into &amp;ldquo;a module you can ship to production and maintain for years.&amp;rdquo;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
