<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Roslyn on Hermit Blog</title><link>https://hermit.no/categories/roslyn/</link><description>Recent content in Roslyn on Hermit Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 03 Nov 2018 21:51:11 +0100</lastBuildDate><atom:link href="https://hermit.no/categories/roslyn/index.xml" rel="self" type="application/rss+xml"/><item><title>How to convert NUnit Assert.AreEqual to fluent Assert.That syntax easily</title><link>https://hermit.no/archive/2018-11-03-how-to-convert-nunit-assert-areequal-to-fluent-assert-that-syntax-easily/</link><pubDate>Sat, 03 Nov 2018 21:51:11 +0100</pubDate><guid>https://hermit.no/archive/2018-11-03-how-to-convert-nunit-assert-areequal-to-fluent-assert-that-syntax-easily/</guid><description>&lt;p&gt;Once upon a time it was declared that an Assert statement should have constraints given as AreEqual and AreNotEqual. Further it was declared that it should be written in the opposite way of how a developer will think, that is with the expected value first and the actual value last. Why this was made so, is still unclear.&lt;/p&gt;&#10;&lt;p&gt;And then we end up with tons of code like:&lt;/p&gt;&#10;&lt;p&gt;&lt;code&gt;Assert.AreEqual(&amp;ldquo;Zulu&amp;rdquo;, zulu.Name);&#10;Assert.AreEqual(&amp;ldquo;Z - Zulu&amp;rdquo;, zulu.Description);&#10;Assert.AreEqual(FlagType.Signal, zulu.Sort);&#10;Assert.AreEqual(0.7, zulu.AspectRatio);&lt;/code&gt;&lt;/p&gt;</description></item></channel></rss>