<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Feature Interaction on Hillel Wayne</title>
    <link>https://www.hillelwayne.com/tags/feature-interaction/</link>
    <description>Recent content in Feature Interaction on Hillel Wayne</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 05 Feb 2020 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.hillelwayne.com/tags/feature-interaction/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Feature Interaction Bugs</title>
      <link>https://www.hillelwayne.com/post/feature-interaction/</link>
      <pubDate>Wed, 05 Feb 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.hillelwayne.com/post/feature-interaction/</guid>
      <description>In most testing frameworks, you&amp;rsquo;re expected to write a lot of low-level tests and few high-level tests. The reasoning is that end-to-end tests are slow and expensive and only cover a tiny amount of the program&amp;rsquo;s state space. It&amp;rsquo;s better to focus on testing all the parts in isolation versus testing that they all work together.
In practice, global correctness does not follow from local correctness. It&amp;rsquo;s possible for every part to be individually rock-solid but the system to be broken as a whole.</description>
    </item>
    
  </channel>
</rss>