<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>UnitTests on On The Drift</title><link>https://www.onthedrift.com/tags/unittests/</link><description>Recent content in UnitTests on On The Drift</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><managingEditor>koen@linker.io (Koen)</managingEditor><webMaster>koen@linker.io (Koen)</webMaster><lastBuildDate>Mon, 03 May 2021 00:00:00 +0000</lastBuildDate><atom:link href="https://www.onthedrift.com/tags/unittests/index.xml" rel="self" type="application/rss+xml"/><item><title>Introducing ScenarioTests, an experiment in improving the .NET testing experience</title><link>https://www.onthedrift.com/posts/scenario-tests/</link><pubDate>Mon, 03 May 2021 00:00:00 +0000</pubDate><author>koen@linker.io (Koen)</author><guid>https://www.onthedrift.com/posts/scenario-tests/</guid><description>&lt;p>When developing software, you&amp;rsquo;ll sooner or later be confronted with the notion of Tests. In the .NET landscape we have plenty of &lt;a href="https://docs.microsoft.com/en-us/dotnet/core/testing/">tools&lt;/a> at our disposal to help us test our code. In this post I&amp;rsquo;d like to introduce &lt;a href="https://github.com/koenbeuk/ScenarioTests">ScenarioTests&lt;/a>. A new project that aims to make testing in .NET better.&lt;/p></description></item></channel></rss>