<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Refactoring - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Refactoring Articles feed</description>
    <item>
      <title>Article: Is Your Test Suite Brittle? Maybe It’s Too DRY</title>
      <link>https://www.infoq.com/articles/brittle-test-suite-maybe-too-dry/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Refactoring-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/brittle-test-suite-maybe-too-dry/en/headerimage/is-your-test-suite-brittle-maybe-its-too-DRY-header-1713945017743.jpg"/&gt;&lt;p&gt;One important design principle in software development is DRY – Don’t Repeat Yourself. However, when DRY is applied to test code, it can cause the test suite to become brittle — difficult to understand, maintain, and change. In this article, I will present some indications that a test suite is brittle, guidelines to follow when reducing duplication in tests, and better ways to DRY up tests.&lt;/p&gt; &lt;i&gt;By Kimberly Hendrick&lt;/i&gt;</description>
      <category>Clean Code</category>
      <category>Integration Testing</category>
      <category>Refactoring</category>
      <category>Unit Testing</category>
      <category>Test Driven</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Fri, 26 Apr 2024 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/brittle-test-suite-maybe-too-dry/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Refactoring-articles</guid>
      <dc:creator>Kimberly Hendrick</dc:creator>
      <dc:date>2024-04-26T09:00:00Z</dc:date>
      <dc:identifier>/articles/brittle-test-suite-maybe-too-dry/en</dc:identifier>
    </item>
  </channel>
</rss>
