<?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 Kuldeep Pisda</title><link>https://kdpisda.in/tag/testing/</link><description>Recent content in Testing on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 15 Jul 2026 08:00:00 +0200</lastBuildDate><atom:link href="https://kdpisda.in/tag/testing/index.xml" rel="self" type="application/rss+xml"/><item><title>Django TDD Patterns: A Visual Field Guide</title><link>https://kdpisda.in/django-tdd-patterns-visual-field-guide/</link><pubDate>Wed, 15 Jul 2026 08:00:00 +0200</pubDate><guid>https://kdpisda.in/django-tdd-patterns-visual-field-guide/</guid><description>&lt;p&gt;Most Django testing tutorials stop at the basics: &amp;ldquo;write a test, watch it fail, make it pass, refactor.&amp;rdquo; While this sounds great in theory, real-world Django applications are infinitely more complex.&lt;/p&gt;
&lt;p&gt;Is TDD even the right framework for apps that are mostly CRUD and ORM glue? Honestly, the case is weaker there—you already know the shape of the interface. TDD earns its keep at the seams: tangled model relationships, multi-layered permission systems, state transitions, and third-party API integrations. That is exactly why this guide focuses there instead of trivial model CRUD.&lt;/p&gt;</description></item></channel></rss>