<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - TDD</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ TDD feed</description>
    <item>
      <title>Getting Feedback from Test-Driven Development and Testing in Production</title>
      <link>https://www.infoq.com/news/2026/02/feedback-TDD-production/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=TDD</link>
      <description>&lt;img src="https://res.infoq.com/news/2026/02/feedback-TDD-production/en/headerimage/generatedHeaderImage-1770047803836.jpg"/&gt;&lt;p&gt;Teams rely on strong unit and integration tests instead of end-to-end tests. Using TDD, pair programming, and good design, they ship small changes often, test in production for real feedback, and use feature toggles to reduce risk, Ola Hast and Asgaut Mjølne Söderbom mentioned in their talk about continuous delivery with pair programming.&lt;/p&gt; &lt;i&gt;By Ben Linders&lt;/i&gt;</description>
      <category>Risk Management</category>
      <category>Feedback</category>
      <category>Integration Test</category>
      <category>Continuous Integration</category>
      <category>QCon London 2025</category>
      <category>QCon Software Development Conference</category>
      <category>Pair Programming</category>
      <category>TDD</category>
      <category>Culture &amp; Methods</category>
      <category>Development</category>
      <category>news</category>
      <pubDate>Thu, 05 Feb 2026 11:36:00 GMT</pubDate>
      <guid>https://www.infoq.com/news/2026/02/feedback-TDD-production/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=TDD</guid>
      <dc:creator>Ben Linders</dc:creator>
      <dc:date>2026-02-05T11:36:00Z</dc:date>
      <dc:identifier>/news/2026/02/feedback-TDD-production/en</dc:identifier>
    </item>
  </channel>
</rss>
