<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing on Chen Kai Blog</title><link>https://www.chenk.top/en/tags/testing/</link><description>Recent content in Testing on Chen Kai Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 14 Apr 2022 09:00:00 +0000</lastBuildDate><atom:link href="https://www.chenk.top/en/tags/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Python Engineering (3): Testing — pytest, Fixtures, and the Confidence Loop</title><link>https://www.chenk.top/en/python-engineering/03-testing-and-debugging/</link><pubDate>Thu, 14 Apr 2022 09:00:00 +0000</pubDate><guid>https://www.chenk.top/en/python-engineering/03-testing-and-debugging/</guid><description>&lt;p>You change one line and three unrelated features break. You refactor a function and spend two hours manually clicking through the app to check if everything still works. You deploy on Friday and get paged at midnight. All of these are symptoms of the same disease: no tests.&lt;/p>
&lt;p>Tests are not bureaucracy. They are the fastest way to know that your code does what you think it does. A good test suite runs in seconds and catches the bugs that would take hours to find manually.&lt;/p></description></item></channel></rss>