<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Tunit on Dimitri Laaraybi</title>
    <link>https://www.dimitrilaaraybi.com/tags/tunit/</link>
    <description>Recent content in Tunit on Dimitri Laaraybi</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 27 Jan 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.dimitrilaaraybi.com/tags/tunit/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Exploring TUnit, a modern take on .NET testing</title>
      <link>https://www.dimitrilaaraybi.com/blog/tunit/</link>
      <pubDate>Tue, 27 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://www.dimitrilaaraybi.com/blog/tunit/</guid>
      <description>&lt;p&gt;The .NET testing ecosystem has been dominated for years by well‑established frameworks such as &lt;strong&gt;xUnit&lt;/strong&gt;, &lt;strong&gt;NUnit&lt;/strong&gt;, and &lt;strong&gt;MSTest&lt;/strong&gt;. They are mature, stable, and battle‑tested. But as .NET itself evolves, becoming faster, more async‑friendly, and more careful about performance, new tools are emerging to better match these modern expectations.&lt;/p&gt;&#xA;&lt;p&gt;One of the most interesting newcomers is &lt;strong&gt;&lt;a href=&#34;https://tunit.dev/&#34;&#xA;    target=&#34;_blank&#34; rel=&#34;noopener&#34;&gt;&#xA;  TUnit&#xA;&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;In this article, we’ll try to explore what TUnit is, its core concepts and advantages, but also explore concrete examples of tests compared to xUnit.&lt;br&gt;&#xA;Let&amp;rsquo;s go ! 🔥&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
