<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Asynchronous Systems on Nalar</title>
    <link>https://nalar.dev/tags/asynchronous-systems/</link>
    <description>Recent content in Asynchronous Systems on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/asynchronous-systems/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Testing Asynchronous Behavior with Eventual Assertions</title>
      <link>https://nalar.dev/testing-asynchronous-behavior-with-eventual-assertions/</link>
      <pubDate>Thu, 10 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/testing-asynchronous-behavior-with-eventual-assertions/</guid>
      <description>&lt;h1 id=&#34;testing-asynchronous-behavior-with-eventual-assertions&#34;&gt;Testing Asynchronous Behavior with Eventual Assertions&lt;/h1&gt;&#xA;&lt;p&gt;A test starts background work and then checks the result. On a fast machine the work finishes first and the test passes. Under CI load, the assertion runs a few milliseconds earlier and fails. Someone adds &lt;code&gt;sleep(1 second)&lt;/code&gt;. The failure disappears, but every successful run now pays a full second, and a sufficiently slow run can still fail.&lt;/p&gt;&#xA;&lt;p&gt;The problem is not that the test needs a longer delay. The test doesn&amp;rsquo;t know exactly when the result will become observable.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
