How eunkyoungjung/dear-my-python-testing-goat works
Project type and purpose
• This is a monolithic, full-stack Django web application scaffolded around the “superlists” tutorial (a to-do list app).
• It follows Test-Driven Development (TDD) practices, with functional tests (functional_test.py) and unit tests (lists/tests.py).
File structure
Top level:
• manage.py – Django’s CLI entry point
• requirements.txt – Python dependencies (Django, Selenium, etc.)
• functional_test.py – end-to-end test harness (likely using Selenium)
• README.md – describes TDD workflow
superlists/ (project config):
• settings.py, urls.py, wsgi.py/asgi.py
lists/ (Django app):
• models.py – ORM models (List, Item)
• views.py – request handlers
• templates/home.html – HTML template
• migrations/ – schema change history
• tests.py – unit tests
README for additional insights
• Emphasizes functional vs. unit tests and the TDD cycle.
Elements
• Labels for each component (e.g., “Browser”, “Django URLconf”).
– User/Test → HTTP server
– Server → DB and back
– Server → Templates → Client
Detailed capture of essential architecture
a) URL dispatcher (urls.py)
b) View layer (lists/views.py)
c) Model layer (lists/models.py + migrations)
d) Template engine (lists/templates/home.html)
Final advice
• Use clear, consistent naming matching your code.
• TDD approach by placing test components alongside their targets.