Testing

[ndarville]

Categories

See Django’s Nasal Passage.

Resources

• http://www.tdd-django-tutorial.com/
• https://github.com/hjwp/Test-Driven-Django-Tutorial/tree/master/mysite/polls/tests
• http://lincolnloop.com/blog/2012/nov/2/introduction-django-selenium-testing/

[ndarville]

Tests:

1. Model
2. View
3. Form
4. Template/Functional—not using the admin
5. Installed/Apps

---

Functional tests = view tests + template tests + model tests <=> F = V + T + M.

In other words, is there a reason you would want to separate the two—at least for simple projects? Perhaps for very granular, exhaustive testing.

I guess not. So instead we get:

1. Deploy (Travis CI)
2. Form
3. Installed Apps
4. Functional
   1. Model (shell)
   2. View
      • Account back-end
      • Settings
      • Bans
   3. Template
5. Configuration
   • Security (django-secure)
   • E-mail settings/Site settings
     • Prevent users from registering if
     • Not configured
     • !'registration.backends.simple.urls'

To start with, model, view, and template tests should just be subsumed under functional tests, until the basic, general tests are done. After that, a granular approach with more exhaustive cases can be developed.

---

Figure out how to build a test matrix. E.g.: view a URL, and perform a battery of actions as an admin, registered, banned, and anonymous user.

[ndarville]

Basic tests done for now. Revisit later.