<?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 Scholion</title><link>https://scholion.thluiz.com/tags/mocks/</link><description>Recent content in Mocks on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Sat, 02 Jan 2016 13:57:17 -0300</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/mocks/index.xml" rel="self" type="application/rss+xml"/><item><title>Mocks and explicit contracts</title><link>https://scholion.thluiz.com/notes/mocks-and-explicit-contracts/</link><pubDate>Sat, 02 Jan 2016 13:57:17 -0300</pubDate><guid>https://scholion.thluiz.com/notes/mocks-and-explicit-contracts/</guid><description>The post argues that mocks are useful, but only when they replace a real dependency through an explicit contract. That keeps tests isolated, makes boundaries visible, and avoids coupling to implementation details.</description></item></channel></rss>