<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>TDD on Matt Sencenbaugh</title>
    <link>https://mattsencenbaugh.com/tags/tdd/</link>
    <description>Recent content in TDD on Matt Sencenbaugh</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Thu, 26 Jan 2023 00:00:00 +0000</lastBuildDate><atom:link href="https://mattsencenbaugh.com/tags/tdd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Invert your assertions</title>
      <link>https://mattsencenbaugh.com/invert-your-assertions/</link>
      <pubDate>Thu, 26 Jan 2023 00:00:00 +0000</pubDate>
      
      <guid>https://mattsencenbaugh.com/invert-your-assertions/</guid>
      <description>TDD Tip: Invert your assertion One top tip I picked up years ago from a co-worker was to invert your assertions when you are in the midst of your TDD cycles.
In other words, if you have an RSpec assertion like this:
expect(foo.nil?).to be_truthy
flip the truthy to falsey and run the test
expect(foo.nil?).to be_falsey
What you want to see there is that your test fails. In a &amp;lsquo;true&amp;rsquo; TDD environment the test would be perfectly clean and no state would be acting on your subject, but that&amp;rsquo;s just not how most test suites for production products work.</description>
    </item>
    
  </channel>
</rss>
