Rename chapter 22 outside in

Author: hjwp

.gitmodules

@@ -53,7 +53,7 @@
 	path = source/chapter_21_server_side_debugging/superlists
 	url = [email protected]:hjwp/book-example.git
 [submodule "source/chapter_19/superlists"]
-	path = source/chapter_outside_in/superlists
+	path = source/chapter_22_outside_in/superlists
 	url = [email protected]:hjwp/book-example.git
 [submodule "source/chapter_20/superlists"]
 	path = source/chapter_purist_unit_tests/superlists

Makefile

@@ -137,9 +137,9 @@ test_chapter_20_fixtures_and_wait_decorator: chapter_20_fixtures_and_wait_decora
 .PHONY: test_chapter_21_server_side_debugging
 test_chapter_21_server_side_debugging: chapter_21_server_side_debugging.html $(TMPDIR) $(VENV)/bin
 	$(VENV)/bin/pytest -s --tb=short ./tests/test_chapter_21_server_side_debugging.py
-.PHONY: test_chapter_outside_in
-test_chapter_outside_in: chapter_outside_in.html $(TMPDIR) $(VENV)/bin
-	$(VENV)/bin/pytest -s --tb=short ./tests/test_chapter_outside_in.py
+.PHONY: test_chapter_22_outside_in
+test_chapter_22_outside_in: chapter_22_outside_in.html $(TMPDIR) $(VENV)/bin
+	$(VENV)/bin/pytest -s --tb=short ./tests/test_chapter_22_outside_in.py
 .PHONY: test_chapter_purist_unit_tests
 test_chapter_purist_unit_tests: chapter_purist_unit_tests.html $(TMPDIR) $(VENV)/bin
 	$(VENV)/bin/pytest -s --tb=short ./tests/test_chapter_purist_unit_tests.py

appendix_IX_cheat_sheet.asciidoc

@@ -161,6 +161,6 @@ If you do find yourself writing tests with lots of mocks, and they feel
 painful, remember “__listen to your tests__”—ugly, mocky tests may be
 trying to tell you that your code could be simplified.
 
-Relevant chapters: <<chapter_outside_in>>, <<chapter_purist_unit_tests>>,
+Relevant chapters: <<chapter_22_outside_in>>, <<chapter_purist_unit_tests>>,
 <<chapter_hot_lava>>
 

appendix_bdd.asciidoc

@@ -43,7 +43,7 @@ https://pythonhosted.org/behave-django/[behave-django].
 **********************************************************************
 
 ((("code examples, obtaining and using")))I'm
-going to use the example from <<chapter_outside_in>>. 
+going to use the example from <<chapter_22_outside_in>>. 
 We have a basic to-do lists site, and we want to add a new feature:
 logged-in users should be able to view the lists they've authored in one place.
 Up until this point, all lists are effectively anonymous.

appendix_github_links.asciidoc

@@ -40,7 +40,7 @@ Full List of Links for Each Chapter
 <<chapter_19_mocking>>:: https://github.com/hjwp/book-example/tree/chapter_19_mocking
 <<chapter_20_fixtures_and_wait_decorator>>:: https://github.com/hjwp/book-example/tree/chapter_20_fixtures_and_wait_decorator
 <<chapter_21_server_side_debugging>>:: https://github.com/hjwp/book-example/tree/chapter_21_server_side_debugging
-<<chapter_outside_in>>:: https://github.com/hjwp/book-example/tree/chapter_outside_in
+<<chapter_22_outside_in>>:: https://github.com/hjwp/book-example/tree/chapter_22_outside_in
 <<chapter_purist_unit_tests>>:: https://github.com/hjwp/book-example/tree/chapter_purist_unit_tests
 <<chapter_CI>>:: https://github.com/hjwp/book-example/tree/chapter_CI
 <<chapter_page_pattern>>:: https://github.com/hjwp/book-example/tree/chapter_page_pattern

atlas.json

@@ -34,7 +34,7 @@
     "chapter_19_mocking.asciidoc",
     "chapter_20_fixtures_and_wait_decorator.asciidoc",
     "chapter_21_server_side_debugging.asciidoc",
-    "chapter_outside_in.asciidoc",
+    "chapter_22_outside_in.asciidoc",
     "chapter_purist_unit_tests.asciidoc",
     "chapter_CI.asciidoc",
     "chapter_page_pattern.asciidoc",

book.asciidoc

@@ -45,7 +45,7 @@ include::chapter_18_spiking_custom_auth.asciidoc[]
 include::chapter_19_mocking.asciidoc[]
 include::chapter_20_fixtures_and_wait_decorator.asciidoc[]
 include::chapter_21_server_side_debugging.asciidoc[]
-include::chapter_outside_in.asciidoc[]
+include::chapter_22_outside_in.asciidoc[]
 include::chapter_purist_unit_tests.asciidoc[]
 include::chapter_CI.asciidoc[]
 include::chapter_page_pattern.asciidoc[]

chapter_07_working_incrementally.asciidoc

@@ -2543,7 +2543,7 @@ YAGNI::
     just because it suggests itself at the time.
     Chances are, you won't use it,
     or you won't have anticipated your future requirements correctly.
-     See <<chapter_outside_in>> for one methodology that helps us avoid this trap.
+     See <<chapter_22_outside_in>> for one methodology that helps us avoid this trap.
     ((("Test-Driven Development (TDD)", "philosophy of", "YAGNI")))
     ((("YAGNI (You ain&#x2019;t gonna need it!)")))
 

chapter_outside_in.asciidoc renamed to chapter_22_outside_in.asciidoc

@@ -1,4 +1,4 @@
-[[chapter_outside_in]]
+[[chapter_22_outside_in]]
 Finishing "My Lists": Outside-In TDD
 ------------------------------------