<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Unit-Testing on Karpoke - Just Another Blog</title><link>http://karpoke.ignaciocano.com/tags/unit-testing/</link><description>Recent content in Unit-Testing on Karpoke - Just Another Blog</description><generator>Hugo -- 0.167.0</generator><language>es</language><lastBuildDate>Thu, 24 Feb 2022 09:44:51 +0100</lastBuildDate><atom:link href="http://karpoke.ignaciocano.com/tags/unit-testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Why You Need to Stop Writing Unit Tests</title><link>http://karpoke.ignaciocano.com/2022/02/24/why-you-need-to-stop-writing-unit-tests/</link><pubDate>Thu, 24 Feb 2022 09:44:51 +0100</pubDate><guid>http://karpoke.ignaciocano.com/2022/02/24/why-you-need-to-stop-writing-unit-tests/</guid><description>&lt;blockquote&gt;
&lt;p&gt;The way you test has a huge impact on your codebase maintainability.
There is a simple way to improve it&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;» hackernoon.com | &lt;a href="https://hackernoon.com/why-you-need-to-stop-writing-unit-tests"&gt;hackernoon.com&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>