การเขียน TestCase และคำยืนยัน

Tests catch bugs before your users do. They let you change code with confidence, knowing a green run means nothing broke. ✅

Django gives you a TestCase base class. Subclass it and each method that starts with test_ becomes an automatic check.

Group related checks in one class. Here a TestCase subclass will hold all the tests for the Article model.

TestCase runs each test in its own transaction and rolls it back afterward. Tests never pollute your real data or each other.

Name every test method with a test_ prefix so Django's runner discovers and executes it for you.

The classic check is assertEqual. It passes when two values match and fails loudly when they differ.

For boolean conditions use assertTrue and assertFalse. They make intent crystal clear in your test.

Need the same object in many tests? Build it once in setUp, which Django runs before every test method.

Verify your model behaves as designed. Create an object, call its method, then assert the result is what you expect.

Kick everything off with the test command. Django finds your test files, runs them, and reports passes and failures.

A dot means a pass, an F means a failure, and E means an error. The summary shows exactly which test broke and why.

Django needs to know which methods are tests.

You wrote a TestCase, used setUp for shared data, checked results with assertEqual and assertTrue, and ran it all with manage.py test. 🎉