<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testable-Code on Scholion</title><link>https://scholion.thluiz.com/tags/testable-code/</link><description>Recent content in Testable-Code on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Mon, 16 Nov 2026 15:09:12 +0000</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/testable-code/index.xml" rel="self" type="application/rss+xml"/><item><title>Writing Testable JavaScript</title><link>https://scholion.thluiz.com/notes/writing-testable-javascript/</link><pubDate>Sat, 22 Feb 2020 12:11:49 +0000</pubDate><guid>https://scholion.thluiz.com/notes/writing-testable-javascript/</guid><description>The article argues that unit testing becomes practical when JavaScript is split into small, testable pieces with clear responsibilities, simple methods, and configurable objects.</description></item><item><title>How I Write Testable Code | Khalil's Simple Methodology | Khalil Stemmler</title><link>https://scholion.thluiz.com/notes/how-i-write-testable-code-khalil-stemmler/</link><pubDate>Sat, 22 Feb 2020 12:11:45 +0000</pubDate><guid>https://scholion.thluiz.com/notes/how-i-write-testable-code-khalil-stemmler/</guid><description>The article argues that testability depends on how dependencies are introduced. Prefer abstractions, same-layer or inner-layer dependencies, or stable dependencies, and use dependency inversion when a dependency makes testing hard.</description></item></channel></rss>