<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing on Daniel Lyons</title><link>https://dandylyons.net/topics/testing/</link><description>Recent content in Testing on Daniel Lyons</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><lastBuildDate>Tue, 20 Aug 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://dandylyons.net/topics/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Exhaustive Testing Made Easy</title><link>https://dandylyons.net/posts/exhaustive-testing-made-easy/</link><pubDate>Tue, 20 Aug 2024 00:00:00 +0000</pubDate><guid>https://dandylyons.net/posts/exhaustive-testing-made-easy/</guid><description>&lt;p>Testing is vitally important in virtually any tech stack. That is, unless you want to &lt;a href="https://en.wikipedia.org/wiki/2024_CrowdStrike_incident">shut down 8.5 million computers worldwide&lt;/a>. &lt;sup id="fnref:1">&lt;a href="#fn:1" class="footnote-ref" role="doc-noteref">1&lt;/a>&lt;/sup> Testing is more than a tedious chore. It&amp;rsquo;s an automated warning system of current bugs. What is not automated (at least not entirely) is writing the tests. It takes time to write tests, and we have to know what needs to be tested. No matter how well your tests are written, if your tests don&amp;rsquo;t cover a particular situation, then it won&amp;rsquo;t be caught. This means that we need to assert on every value in our code. This is tedious and error-prone.&lt;/p></description></item></channel></rss>