<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mutation Testing on JAVAPRO International</title><link>https://javapro-en.svenruppert.com/tags/mutation-testing/</link><description>Recent content in Mutation Testing on JAVAPRO International</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 21 Jan 2026 07:00:03 +0000</lastBuildDate><atom:link href="https://javapro-en.svenruppert.com/tags/mutation-testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Test Your Tests: Mutation Testing in Java with PIT</title><link>https://javapro-en.svenruppert.com/test-your-tests-mutation-testing-in-java-with-pit/</link><pubDate>Wed, 21 Jan 2026 07:00:03 +0000</pubDate><guid>https://javapro-en.svenruppert.com/test-your-tests-mutation-testing-in-java-with-pit/</guid><description>&lt;h2 id="beyond-code-coverage"&gt;Beyond Code Coverage&lt;/h2&gt;
&lt;p&gt;Automated tests have become a standard component of professional software development. Whether through classic unit testing or a fully test-driven development (TDD) workflow, tests help to ensure that applications are correct, maintainable, and refactorable. Most development teams track code coverage using tools such as JaCoCo and integrate these metrics into their CI/CD pipelines. At first glance, this seems sufficient: high test coverage and we are safe – right?&lt;/p&gt;</description></item></channel></rss>