https://www.rohitjha.dev/tags/model-based-testing/Recent content in Model-Based Testing on Rohit JhaHugoen-US© Rohit Jha. Articles licensed under CC BY-SA 4.0 unless noted.Sun, 13 Sep 2026 20:35:34 +0530https://www.rohitjha.dev/blog/model-based-testing-in-go/Sun, 13 Sep 2026 00:00:00 +0000https://www.rohitjha.dev/blog/model-based-testing-in-go/<p>In my previous post on <a href="https://www.rohitjha.dev/blog/property-based-testing-in-go/">property-based testing in Go</a>, I generated values and checked properties such as serialization round trips and stable event IDs. Each generated value was one test case.</p> <p>Many of the failures I care about in distributed systems depend on history instead. Each operation in a booking system may pass its own unit tests while the lifecycle still mishandles a sequence such as:</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">create </span></span><span class="line"><span class="cl">confirm </span></span><span class="line"><span class="cl">cancel </span></span><span class="line"><span class="cl">confirm </span></span></code></pre></div><p>The last confirmation should be rejected. Other failures need less obvious histories: a retry applies an effect twice, a delayed command reopens a cancelled booking, or a rejected command changes state before returning an error.</p>