<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Grambling on Hillel Wayne</title>
    <link>https://www.hillelwayne.com/tags/grambling/</link>
    <description>Recent content in Grambling on Hillel Wayne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 26 Oct 2017 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.hillelwayne.com/tags/grambling/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Unit Tests Aren&#39;t Tests</title>
      <link>https://www.hillelwayne.com/post/unit-tests-are-not-tests/</link>
      <pubDate>Thu, 26 Oct 2017 00:00:00 +0000</pubDate>
      
      <guid>https://www.hillelwayne.com/post/unit-tests-are-not-tests/</guid>
      <description>This is an absolutely insane idea and I&amp;rsquo;m delighted by its audacity so I&amp;rsquo;m sharing it with all y&amp;rsquo;all. There&amp;rsquo;s like a bazillion things wrong with it but saying dumb shit has never stopped me before so let&amp;rsquo;s do some grambling!
The way I see it, unit tests act as a frame around your coding. The most common practice is you write the tests to cover the return values and calls, write your code, and enforce that it passes the unit tests.</description>
    </item>
    
  </channel>
</rss>