<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Mocks on vnykmshr</title><link>https://blog.vnykmshr.com/writing/tags/mocks/</link><description>Recent content in Mocks on vnykmshr</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 21 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.vnykmshr.com/writing/tags/mocks/index.xml" rel="self" type="application/rss+xml"/><item><title>The wrong test</title><link>https://blog.vnykmshr.com/writing/the-wrong-test/</link><pubDate>Tue, 21 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.vnykmshr.com/writing/the-wrong-test/</guid><description>&lt;p&gt;100% test coverage and a broken migration. Same week.&lt;/p&gt;
&lt;p&gt;The suite was green. CI was green. The deploy was green. The migration ran on a Tuesday afternoon and dropped a column something was still reading from. Every test that would have caught it was mocked against a schema the fixture hadn&amp;rsquo;t updated since the quarter before last. The mocks still returned 200. The database didn&amp;rsquo;t.&lt;/p&gt;
&lt;p&gt;Coverage measures what you ran. It does not measure what will happen.&lt;/p&gt;</description></item></channel></rss>