<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing on Michael Hönnig</title><link>https://michael.hoennig.de/en/tags/Testing/</link><description>Recent content in Testing on Michael Hönnig</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>© 2026 Michael Hönnig</copyright><lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0100</lastBuildDate><atom:link href="https://michael.hoennig.de/en/tags/Testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Not Unit Tests, but Our Units Are the Problem</title><link>https://michael.hoennig.de/en/blog/2026/2026-11-17-unit-tests-module-depth/</link><pubDate>Tue, 17 Nov 2026 00:00:00 +0100</pubDate><guid>https://michael.hoennig.de/en/blog/2026/2026-11-17-unit-tests-module-depth/</guid><description>Since coding agents produce huge numbers of fine-grained tests, some demand that we give up unit tests. But the problem is not unit tests, it is units that are defined too small: tests that lock in the current class structure make refactoring harder despite high coverage and a high mutation score. As a measure of refactoring safety, both metrics are incomplete without the tested module depth. The article proposes testing domain components through their public API, determining a module-related mutation score and defining test boundaries as part of the architecture.</description></item></channel></rss>