<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TDD on Artur Rios Lab</title><link>https://lab.artur-rios.tech/tags/tdd/</link><description>Recent content in TDD on Artur Rios Lab</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 20 Oct 2026 22:30:00 +0000</lastBuildDate><atom:link href="https://lab.artur-rios.tech/tags/tdd/index.xml" rel="self" type="application/rss+xml"/><item><title>What Is a Unit Test? Where Unit Testing Came From and How to Write Good Ones</title><link>https://lab.artur-rios.tech/fundamentals/unit-tests/</link><pubDate>Tue, 20 Oct 2026 22:30:00 +0000</pubDate><guid>https://lab.artur-rios.tech/fundamentals/unit-tests/</guid><description>&lt;p&gt;You change one line in a pricing function and want to know whether anything&#10;broke. You could start the whole application, log in, fill a cart and look at&#10;the total, for every kind of cart you can think of. Or you could run a few&#10;hundred small programs that each call the pricing function with one input and&#10;check the answer, and know in under a second. Those small programs are &lt;strong&gt;unit&#10;tests&lt;/strong&gt;, and the second way of working is one of the biggest changes in how&#10;software has been written in the last thirty years: from testing as a phase at&#10;the end of a project, done by someone else, to testing as something every&#10;programmer does every few minutes.&lt;/p&gt;</description></item></channel></rss>