Python
factory_boy is Python's most widely used test object factory library. The basics — factory.Factory and factory.django.DjangoModelFactory — are well documented, but the advanced features are what make large test suites maintainable. This guide covers traits, sub-factories, batch creation, lazy attributes, and the patterns that keep
Testing
Django ships with a solid testing infrastructure built on top of Python's unittest. Most Django developers use 10% of what's available to them.
Testing
pytest-django replaces Django's built-in test runner with pytest, giving you parametrize, fixtures with dependency injection, better output, and a plugin ecosystem that Django's unittest-based runner simply can't match. This tutorial covers the complete setup and the features that matter most in
Testing
Django REST Framework comes with its own testing layer built on top of Django's TestCase.
Testing
N+1 query bugs are silent killers. They pass every functional test, look correct in development, and then crater your production database when traffic hits.
HTMX
HTMX turns Django into a hypermedia-first framework where server responses are HTML fragments (partials) instead of JSON. Testing HTMX with Django means testing two layers: server-side partial rendering (Django TestClient with HX-Request header) and browser-side interaction (Playwright E2E). This guide covers both. Key Takeaways Test partials
Testing
Every Django project starts with the best intentions. You run manage.py startapp, write a few models, and think "I'll add tests later." Later arrives when a migration drops a column your views were querying, and you find out from a 500 error in production. Django