Python测试驱动开发使用Django、Selenium和JavaScript进行Web编程.第2版 ([英]哈利·J.W. 帕西瓦尔,安道译)（Z-Library）

【One-Line Pitch】 A hands-on, project-based guide to Test-Driven Development (TDD) for web applications using Python, Django, Selenium, and JavaScript—ideal for developers who want to build robust, maintainable code by writing tests first and learning by doing. 【Book Arc】 - **Opening (~0%–9%)**: Introduces the "Testing Goat" philosophy—write a failing test before any code—and walks through installing Django, setting up a Git repository, and creating the first functional tests with Selenium and unit tests with Python’s `unittest` module. - **Early (~9%–26%)**: Builds a simple to-do list app step-by-step, covering URL routing, view functions, templates, and model design. Emphasizes small, incremental changes, refactoring, and using functional tests to catch regressions as the app grows. - **Early–Middle (~26%–35%)**: Shifts to web development essentials: styling with CSS and Bootstrap, Django template inheritance, and static file handling. Introduces deployment testing on a staging server, covering manual setup with Nginx, Python 3.6, and domain configuration. - **Middle (~35%–48%)**: Focuses on production readiness—switching to Gunicorn, configuring Nginx for static files, setting `DEBUG=False`, and using Systemd for process management. Also covers automating deployment with Fabric and refactoring tests into multiple files. - **Middle–Late (~48%–52%)**: Delves into database-level validation, moving logic from views into Django forms, and using `ModelForm` for cleaner code. Addresses advanced form handling, including uniqueness validation for duplicate to-do items, and introduces JavaScript testing with jQuery and fixtures. 【Key Takeaways】 - **TDD is a discipline, not a tool** (Opening): Write a failing test first, then implement the minimum code to pass it. This "Testing Goat" approach prevents over-engineering and keeps you focused on user needs. - **Functional tests vs. unit tests** (Early): Functional tests (via Selenium) verify the whole system from the user's perspective, while unit tests check specific components. Both are essential—functional tests guide the big picture, unit tests drive the details. - **Incremental design beats upfront planning** (Early): Start with a minimal app and let tests guide each new feature. Use YAGNI ("You Aren't Gonna Need It") to avoid speculative complexity, and refactor only when tests are green. - **Deployment is part of TDD** (Middle): Test deployment early on a staging server to catch environment-specific issues. Manual setup (Nginx, Gunicorn, virtualenv) teaches you the stack before automating it with tools like Fabric. - **Forms centralize validation** (Middle–Late): Move validation logic from views into Django forms (especially `ModelForm`) to reduce duplication and make tests cleaner. This also unlocks free benefits like HTML5 client-side validation. - **JavaScript needs its own test strategy** (Late): Use a basic test runner, jQuery, and `<div>` fixtures to unit-test JavaScript behavior. Manage global state and execution order carefully—these are the biggest challenges in JS testing. 【Reading Tips】 - **Skim the early setup chapters** (~0%–9%) if you already know Django basics; focus instead on the TDD workflow and how functional tests are structured. - **Deep-read the to-do list build** (~9%–26%)—this is the core of the book. Follow along by coding, not just reading; the value is in the repetition of test-fail-pass-refactor. - **Pay attention to deployment chapters** (~30%–43%) even if you use PaaS; understanding manual Nginx/Gunicorn setup clarifies what automation tools do under the hood. - **Treat Chapter 13–15 as a unit** (~43%–52%): They show a realistic refactoring journey from views to forms. Read them together to see how validation evolves. - **Skip the JavaScript chapter** (~52%) if you're not using client-side interactivity; it's useful but somewhat isolated from the Django core. 【Coverage Limits】 This guide synthesizes the book's structure and key themes from the provided excerpts, which cover roughly the first half of the book (up to ~52%). Later topics like mocking, third-party authentication, Ajax, test fixtures, and continuous integration are mentioned in the blurb but not detailed in the excerpts.