El cliente de pruebas y los fixtures

Model tests are great, but you also want to test full pages. The test client lets you simulate a real browser request inside a test. 🌐

Every TestCase gives you a self.client for free. No setup needed, it is wired up and waiting in each test.

Call self.client.get with a URL to fetch a page just like a browser would, then inspect what comes back.

The response carries a status_code. Assert it equals 200 to confirm the page loaded successfully.

Django offers a shortcut. Use assertContains to confirm both a 200 status and that expected text is on the page.

Simulate a form submission with self.client.post, passing a dictionary of the fields a user would fill in.

Hardcoded URLs break easily. Use reverse to look up the URL from its route name instead.

A fixture is a file of pre-built rows. It seeds your test database so every test starts with the same known data.

Export existing rows with dumpdata. Django writes them to JSON that you can replay later as a fixture.

List your fixture files in the fixtures attribute and Django loads them automatically before each test runs.

Reach for fixtures when you need a fixed dataset to load fast, and setUp when each test needs small, tailored objects.

You drove views with the test client, checked status and content, posted form data, and seeded data with fixtures and dumpdata. 🎉