<?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>Mutation-Testing on Tomás Dias Almeida notes</title>
    <link>https://tomasalmeida.pro/tags/mutation-testing/</link>
    <description>Recent content in Mutation-Testing on Tomás Dias Almeida notes</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 10 Nov 2026 20:14:46 +0100</lastBuildDate>
    <atom:link href="https://tomasalmeida.pro/tags/mutation-testing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Mutation Testing for AI-Generated Code and Tests</title>
      <link>https://tomasalmeida.pro/posts/2026/11/mutation-testing-ai-generated-code/</link>
      <pubDate>Tue, 10 Nov 2026 12:00:00 +0100</pubDate>
      <guid>https://tomasalmeida.pro/posts/2026/11/mutation-testing-ai-generated-code/</guid>
      <description>&lt;p&gt;AI coding assistants can generate a working implementation in a few seconds. They can also generate a test suite that passes in the same amount of time. That speed is useful, but a green test run does not tell us whether the tests would catch a real defect.&lt;/p&gt;
&lt;p&gt;Mutation testing gives us a practical way to check that question. A mutation tool makes small changes to the production code, runs the test suite, and reports which changes the tests detected. The changed programs are called mutants. A test suite that fails when a mutant is present has killed that mutant. A surviving mutant shows a behavior that the tests did not distinguish.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
