some handwritten todos

Author: hjwp

chapter_18_spiking_custom_auth.asciidoc

@@ -12,7 +12,7 @@ so please send feedback!  [email protected]
 
 *******************************************************************************
 
-((("authentication", id="Adespike18")))
+((("authentication", id="AuthSpike18")))
 Our beautiful lists site has been live for a few days, and our users are
 starting to come back to us with feedback.  "We love the site", they say, "but
 we keep losing our lists.  Manually remembering URLs is hard. It'd be great if
@@ -883,7 +883,7 @@ Next let's rebuild our minimal user model, with tests this time, and see
 if it turns out neater than it did in the spike.
 ((("", startref="SDde18")))
 
-
+// TODO: consider starting with a test for the login view instead.
 
 === A Minimal Custom User Model
 
@@ -1353,6 +1353,6 @@ Writing your FT against spiked code::
     reimplementing a very similar solution to your spiked one;
     something to watch out for.
     ((("functional tests (FTs)", "spiked code and")))
-    ((("", startref="Adespike18")))
+    ((("", startref="AuthSpike18")))
 *******************************************************************************
 

chapter_mocking.asciidoc

@@ -22,7 +22,7 @@ any emails it sends by using the `mail.outbox` attribute.
 But in this chapter, I want to demonstrate a very important testing technique called 'mocking',
 so for the purpose of these unit tests, we'll pretend that this nice Django shortcut doesn't exist.
 
-Am I telling you not to use Django's `mail.outbox`?
+Am I telling you _not_ to use Django's `mail.outbox`?
 No; use it, it's a neat shortcut.
 But I want to teach mocks because they're a useful general-purpose tool
 for unit testing external dependencies.

todos.txt

@@ -2,6 +2,14 @@
 
 # Later
 
+- spike chap:  start with test of login view.
+- count all TR notes per chapter
+- massive updates in 11
+- idea, get rid of model-layer tests
+- "switch to flask" appendix
+
+
+
 * rewrites