<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>pytest on Rise-</title><link>https://madil.in/tag/pytest/</link><description>Recent content in pytest on Rise-</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 07 Jun 2026 08:06:40 +0000</lastBuildDate><atom:link href="https://madil.in/tag/pytest/index.xml" rel="self" type="application/rss+xml"/><item><title>Testing Anti-Patterns You Need to Stop Using</title><link>https://madil.in/testing-anti-patterns-you-need-to-stop-using/</link><pubDate>Sun, 24 May 2026 14:45:14 +0000</pubDate><guid>https://madil.in/testing-anti-patterns-you-need-to-stop-using/</guid><description>&lt;p&gt;We write tests to sleep better at night. We write them to catch regressions, document behavior, and confidently ship features to production - even on a Friday afternoon.&lt;/p&gt;&#10;&lt;p&gt;But what happens when your safety net is actually a trap?&lt;/p&gt;&#10;&lt;p&gt;Bad tests are worse than no tests. They give you a false sense of security, grind your CI/CD pipeline to a halt with flaky failures, and turn simple code refactors into week-long debugging nightmares. Over the course of my career, I&amp;rsquo;ve seen test suites slowly devolve from a developer&amp;rsquo;s best friend into their worst enemy.&lt;/p&gt;</description></item></channel></rss>