<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Time on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/time/</link>
    <description>Recent content in Time on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 11 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/time/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Time Mocking in 2026: freezegun vs time-machine vs libfaketime</title>
      <link>https://www.pistack.xyz/posts/2026-11-11-time-mocking-libraries-freezegun-time-machine-libfaketime/</link>
      <pubDate>Wed, 11 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-11-time-mocking-libraries-freezegun-time-machine-libfaketime/</guid>
      <description>&lt;h1 id=&#34;time-mocking-in-2026-freezegun-vs-time-machine-vs-libfaketime&#34;&gt;Time Mocking in 2026: freezegun vs time-machine vs libfaketime&lt;/h1&gt;&#xA;&lt;p&gt;Your suite passes at 11:58 PM and fails at 00:03 AM. Nothing changed in the code — the calendar moved. Any test that touches token expiry, trial periods, retry windows, billing cycles or &amp;ldquo;last 30 days&amp;rdquo; dashboards is a coin flip once the wall clock is an input you never controlled.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
