Django Selenium Functional Tests

Use Selenium functional tests sparingly and deliberately: they prove that Django, templates, static assets, JavaScript, persistence, and browser behavior work together. Keep them user-facing, isolated, and stable enough to inspire confidence.

Source Traceability

Primary source: Harry Percival, Test-Driven Development with Python, 3rd ed. Guidance is transformed and paraphrased from chapters 1, 2, 4, 6, 13, 22, 23, 25, 26, and Appendix A, especially explicit waits, functional test isolation, page pattern, screenshots, and CI debugging.

Workflow

1. State the user journey in comments or helper names.

   • Keep test language at the user behavior level.
   • Avoid asserting implementation details unless the browser contract requires them.

2. Use the right server boundary.

   • Use StaticLiveServerTestCase when static files matter.
   • Use a staging URL or Docker URL when verifying deployed/container behavior.
   • Keep local and remote setup explicit.