<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software-Testing on @zhisme :: signal over noise</title><link>https://zhisme.com/tags/software-testing/</link><description>Recent content in Software-Testing on @zhisme :: signal over noise</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 06 May 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://zhisme.com/tags/software-testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Reviewing "Angry Tests"</title><link>https://zhisme.com/articles/reviewing-angry-tests/</link><pubDate>Tue, 06 May 2025 00:00:00 +0000</pubDate><guid>https://zhisme.com/articles/reviewing-angry-tests/</guid><description>&lt;p>As software engineers, we’re used to writing tests — but we don’t always know how to write them well. We aim to cover the most significant lines of code, often guided by intuition. This book is a practical guide to writing better tests, and I found it to be a valuable resource for anyone involved in software testing — whether you&amp;rsquo;re a developer or a tester.&lt;/p>
&lt;p>You can find the book, purchase options, and more details here:&lt;br>
&lt;a href="https://www.yegor256.com/angry-tests.html" target="_blank" rel="noopener noreferrer">&lt;br>
Yegor&amp;rsquo;s site.&lt;br>
&lt;/a>&lt;br>
This book focuses on automated software testing — &lt;strong>what&lt;/strong> to test, and &lt;strong>how&lt;/strong>. It walks you through best practices and explains why solid testing is essential for long-term maintainability and support.&lt;/p></description></item></channel></rss>