<?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>Linting on Micha Kops&#39; Tech Notes</title>
    <link>https://www.hascode.com/tags/linting/</link>
    <description>Recent content in Linting on Micha Kops&#39; Tech Notes</description>
    <generator>Hugo</generator>
    <language>en</language>
    <copyright>Copyright © 2010 - 2025 Micha Kops. #e9d956c0c0154a221ad83c925346a8fa0e72f866</copyright>
    <lastBuildDate>Tue, 13 Feb 2024 00:00:00 +0100</lastBuildDate>
    <atom:link href="https://www.hascode.com/tags/linting/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Shell Script Testing with Bats</title>
      <link>https://www.hascode.com/shell-script-testing-with-bats/</link>
      <pubDate>Tue, 13 Feb 2024 00:00:00 +0100</pubDate>
      <guid>https://www.hascode.com/shell-script-testing-with-bats/</guid>
      <description>&lt;div id=&#34;preamble&#34;&gt;
&lt;div class=&#34;sectionbody&#34;&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;We’ve all been there: a small shell script that starts as a quick helper suddenly becomes a critical part of your workflow.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;Then one day, it breaks - maybe because of a missing argument, a typo, or an unexpected input.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;Debugging at 2 AM isn’t fun.&lt;/p&gt;
&lt;/div&gt;
&lt;div class=&#34;paragraph&#34;&gt;
&lt;p&gt;That’s why adding tests to your shell scripts is a lifesaver. With Bats (Bash Automated Testing System), you can catch these issues early and make your scripts as reliable as any other piece of software.&lt;/p&gt;
&lt;/div&gt;</description>
    </item>
  </channel>
</rss>
