<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Luajit on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/luajit/</link>
    <description>Recent content in Luajit on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 05 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/luajit/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Lua Testing Frameworks in 2026: Busted vs LuaUnit vs luassert — A Complete Guide</title>
      <link>https://www.pistack.xyz/posts/2026-09-05-lua-testing-frameworks-busted-luaunit-luassert-comparison/</link>
      <pubDate>Sat, 05 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-09-05-lua-testing-frameworks-busted-luaunit-luassert-comparison/</guid>
      <description>&lt;p&gt;Lua has a testing problem that nobody talks about: it&amp;rsquo;s one of the most widely deployed languages on Earth — embedded in Nginx and OpenResty, HAProxy, Redis modules, game engines, and Neovim — yet its test ecosystem is a fraction the size of Python&amp;rsquo;s or JavaScript&amp;rsquo;s. When your Lua code does crash, it&amp;rsquo;s usually inside someone else&amp;rsquo;s host process, which makes testing &lt;em&gt;more&lt;/em&gt; important, not less. The good news: the ecosystem has consolidated around two real frameworks and one essential assertion layer — &lt;strong&gt;Busted&lt;/strong&gt; (1,635 stars, the BDD standard), &lt;strong&gt;LuaUnit&lt;/strong&gt; (633 stars, the single-file xUnit workhorse, now on version 3.5 with Lua 5.5 support), and &lt;strong&gt;luassert&lt;/strong&gt; (250 stars, the extensible assertion and spy engine that powers Busted and works standalone).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
