This is my book about Test-Driven-Development for web programming, published by the excellent O'Reilly Media.
There are a few ways you can read and support this book:
Obviously these are my favourite options! O'Reilly have been great, they deserve your support, and although I only get a small amount in royalties (about a dollar per sale if you're curious), it still pays for the occasional dinner out every month which I appreciate. Plus, real physical books are nice...
TIP: I don't recommend you use Google Play Books, or at least not their PDF version, it's horrible
Alternatively, or in the meantime, help yourself here! It's all free and CC-licenced (thanks O'Reilly!). I see this as a "try-before-you-buy" scheme, and I hope that if you enjoy it you'll buy a copy -- if not for yourself, then perhaps for a friend!
And do get in touch with comments, suggestions, corrections etc! [email protected]
I never announced it on this blog, but I've been working on a 3e for the book, updated for the latest Django and Python. Progress is good so far, I've updated all but 4 of the main chapters, including some major rewrites of the deployment chapters to use Docker and Ansible.
Announcing a new book, "Architecture Patterns with Python", aka Cosmic Python
Being a discussion of abstractions, and how we can use them to reduce unnecessary coupling, make unit testing easier (or possible), and separate core logic from implementation details. Plus some discussion of functional-core-imperative-shell vs dependency injection.
What's been on my mind recently is "architecture stuff" -- kinda where I left off at the end of my book, how to structure your code to be able to get the most out of your tests, but more importantly, manage complexity over time. Would love to know what others are thinking about this...
From time to time we come across a fixture that we want to customise in some way. Factory functions and factory fixtures are classic options, but you can also (mis-) use the pytest parametrize decorator to achieve this goal. Find out how here!
Want to speed up your Django tests? Tell Django to use the special in-memory filesystem at /dev/shm and skip recreating the database...
The second edition is now out in print and ebook, and just needs reviews! (and, you know, as a nice side-effect, sales)
The last big update has landed! The book is now fully upgrade to Python 3.6, and the only version of Django that supports it, 1.11 beta. f-strings a go-go, and a few other nice improvements too.
Well, that was bit of a slog! I've managed to get the book upgraded to the newer version of selenium, and it involved quite a lot of pain with explicit waits, and renumbering all the chapters, but I think the book is better for it. read on!
Progress on the second edition is pretty good! I've got a first cut of some appendices on REST APIs, I've upgraded to Django 1.10, I'm recommending a virtulaenv all the way through, and I've improved the massive Chapter 6 rewrite slog by separating out FTs into one for regression and one for new stuff.
Page 1 / 4 »
"Hands down the best teaching book I've ever read" — "Even the first 4 chapters were worth the money" — "Oh my gosh! This book is outstanding" — "The testing goat is my new friend" — Read more...
The campaign page, preserved for history, which led to the glorious presence of the Testing Goat on the front of the book.