Fakes and the like

Author: orta

README.md

@@ -1,32 +1,29 @@
 A Pragmatic Approach to iOS Testing
 ===============
 
-An ebook about pragmatic testing strategies. Click below to get the latest epub.
+An ebook about pragmatic testing strategies. Click below to get the latest ePub.
 
-[ ![Image](assets/Cover.png "Pragmatic iOS Testing") ](https://github.com/orta/pragmatic-testing/blob/master/pragmatic_testing.epub?raw=true "Download epub")
+[ ![Image](assets/Cover.png "Pragmatic iOS Testing") ](https://github.com/orta/pragmatic-testing/blob/master/pragmatic_testing.epub?raw=true "Download ePub")
 
 Or check [it on GitBook](https://www.gitbook.com/book/orta/pragmatic-ios-testing/details).
 
 Wanna contribute? [read this](CONTRIBUTING.md).
 
 ##### Existing Pages
 
-| Topics | Last Updated | Length | 
+| Topic | Last Updated | Length | 
 | -------|----|-----|
 |[What Is/What And Why Of The Book](chapters/en-UK/what_is/what_and_why_of_the_book.md)|2016-03-31|Words: 518|
 |[What Is/How Can I Be Pragmatic With My Testing](chapters/en-UK/what_is/how_can_i_be_pragmatic_with_my_testing.md)|2016-03-31|Words: 370|
-|[XCTest/Useful Terminology](chapters/en-UK/xctest/useful_terminology.md)|2016-03-31|Words: 105|
-|[XCTest/What Is XCTest How Does It Work](chapters/en-UK/xctest/what_is_xctest_how_does_it_work.md)|2016-03-31|Words: 558|
+|[XCTest/What Is XCTest How Does It Work](chapters/en-UK/xctest/what_is_xctest_how_does_it_work.md)|2016-03-31|Words: 573|
 |[XCTest/Types Of Testing](chapters/en-UK/xctest/types_of_testing.md)|2016-03-31|Words: 216|
 |[XCTest/Unit Testing](chapters/en-UK/xctest/unit_testing.md)|2016-03-31|Words: 336|
 |[XCTest/Behavior Testing](chapters/en-UK/xctest/behavior_testing.md)|2016-03-31|Words: 1228|
 |[XCTest/Three Types Of Unit Tests](chapters/en-UK/xctest/Three_Types_of_Unit_Tests.md)|2016-03-31|Words: 314|
 |[XCTest/Test Driven Development](chapters/en-UK/xctest/test_driven_development.md)|2016-03-31|Words: 233|
 |[XCTest/Integration Testing](chapters/en-UK/xctest/integration_testing.md)|2016-03-31|Words: 536|
-|[XCTest/Testing Terminology](chapters/en-UK/xctest/testing_terminology.md)|2016-03-31|Words: 197|
 |[Foundations/Dependency Injection](chapters/en-UK/foundations/dependency_injection.md)|2016-03-31|Words: 806|
-|[Foundations/Stubs And Mocks](chapters/en-UK/foundations/stubs_and_mocks.md)|2016-03-31|Words: 200|
-|[Foundations/Fakes  Plus Protocols ](chapters/en-UK/foundations/fakes__plus_protocols_.md)|2016-03-31|Words: 151|
+|[Foundations/Stubs Mocks And Fakes](chapters/en-UK/foundations/stubs_mocks_and_fakes.md)||Words: 475|
 |[OSS Libs/Expanding On Bdd Frameworks](chapters/en-UK/oss_libs/expanding_on_bdd_frameworks.md)|2016-03-31|Words: 3|
 |[OSS Libs/Mocking And Stubbing  Ocmock And Ocmockito ](chapters/en-UK/oss_libs/mocking_and_stubbing__ocmock_and_ocmockito_.md)|2016-03-31|Words: 0|
 |[OSS Libs/Network Stubbing  Ohttp And Vcrurlconnection](chapters/en-UK/oss_libs/network_stubbing__ohttp_and_vcrurlconnection.md)|2016-03-31|Words: 0|
@@ -59,9 +56,10 @@ Wanna contribute? [read this](CONTRIBUTING.md).
 |[Wrap Up/Twitter Follows](chapters/en-UK/wrap_up/twitter_follows.md)|2016-03-31|Words: 0|
 |[Wrap Up/Recommended Websites](chapters/en-UK/wrap_up/recommended_websites.md)|2016-03-31|Words: 51|
 
-Over 200 words: 42.2%
-Over 300 words: 37.8%
+
+Over 200 words: 47.6%
+Over 300 words: 42.9%
 
 ##### Generating the ebook
 
-The latest epub copy can be generated by running `ruby generate.rb`
+The latest ePub copy can be generated by running `ruby generate.rb`

SUMMARY.md

@@ -2,18 +2,15 @@
 
 * [Chapters/En-Uk/What Is/What And Why Of The Book](chapters/en-UK/what_is/what_and_why_of_the_book.md)
 * [Chapters/En-Uk/What Is/How Can I Be Pragmatic With My Testing](chapters/en-UK/what_is/how_can_i_be_pragmatic_with_my_testing.md)
-* [Chapters/En-Uk/Xctest/Useful Terminology](chapters/en-UK/xctest/useful_terminology.md)
 * [Chapters/En-Uk/Xctest/What Is Xctest How Does It Work](chapters/en-UK/xctest/what_is_xctest_how_does_it_work.md)
 * [Chapters/En-Uk/Xctest/Types Of Testing](chapters/en-UK/xctest/types_of_testing.md)
 * [Chapters/En-Uk/Xctest/Unit Testing](chapters/en-UK/xctest/unit_testing.md)
 * [Chapters/En-Uk/Xctest/Behavior Testing](chapters/en-UK/xctest/behavior_testing.md)
 * [Chapters/En-Uk/Xctest/Three Types Of Unit Tests](chapters/en-UK/xctest/Three_Types_of_Unit_Tests.md)
 * [Chapters/En-Uk/Xctest/Test Driven Development](chapters/en-UK/xctest/test_driven_development.md)
 * [Chapters/En-Uk/Xctest/Integration Testing](chapters/en-UK/xctest/integration_testing.md)
-* [Chapters/En-Uk/Xctest/Testing Terminology](chapters/en-UK/xctest/testing_terminology.md)
 * [Chapters/En-Uk/Foundations/Dependency Injection](chapters/en-UK/foundations/dependency_injection.md)
-* [Chapters/En-Uk/Foundations/Stubs And Mocks](chapters/en-UK/foundations/stubs_and_mocks.md)
-* [Chapters/En-Uk/Foundations/Fakes  Plus Protocols ](chapters/en-UK/foundations/fakes__plus_protocols_.md)
+* [Chapters/En-Uk/Foundations/Stubs Mocks And Fakes](chapters/en-UK/foundations/stubs_mocks_and_fakes.md)
 * [Chapters/En-Uk/Oss Libs/Expanding On Bdd Frameworks](chapters/en-UK/oss_libs/expanding_on_bdd_frameworks.md)
 * [Chapters/En-Uk/Oss Libs/Mocking And Stubbing  Ocmock And Ocmockito ](chapters/en-UK/oss_libs/mocking_and_stubbing__ocmock_and_ocmockito_.md)
 * [Chapters/En-Uk/Oss Libs/Network Stubbing  Ohttp And Vcrurlconnection](chapters/en-UK/oss_libs/network_stubbing__ohttp_and_vcrurlconnection.md)

chapters/en-UK/foundations/fakes__plus_protocols_.md

@@ -0,0 +1,35 @@
+### Mocks
+
+A mock object is an object created by a library to emulate an existing object's API. In general there are two main types of mocks
+
+1. _Strict Mocks_ - or probably just Mocks. These objects will only respond to what you define upfront, and will assert if they receive anything else.
+
+1. _Nice (or Partial) Mocks_  which wrap existing objects. These mocks objects can define the methods that they should respond too, but will pass any function / messages they haven't been told about to the original.
+
+In Objective-C you can define mocks that act as specific instance of a class, conform to specific protocols or be a class itself. In Swift this is still all up in the air, given the language's strict type system.
+
+### Stubs
+
+A stub is a method that is replaced at runtime with another implementation. It is common for a stub to not call the original method. It's useful in setting up context for when you want to use known a return value with a method.
+
+You can think of it as being method swizzling, really.
+
+### Mocks and Stubs
+
+From a personal opinion I avoid stubbing and mocking code which is under my control.
+
+When you first get started, using Mocks and Stubs feel like the perfect tool for testing code, but it becomes unwieldy as it can quickly get out of sync with reality. They can be a great crutch, when you really can't figure out how to test something however.
+
+A great example of when to use stubbing is when dealing with an Apple class that you cannot easily replace or use your own copy. For example I regularly use partial mocks of `UIScreen` instances in order to emulate being on an iPad simulator when it's actually running on an iPhone simulator. This saves us time from running our test suite twice, sequentially, on multiple simulators.
+
+When you own the code that you're working with, it can often be easier to use a fake.
+
+### Fakes
+
+A Fake is an API compatible version of an object. That is it. Fakes are extremely easy to make in both Swift and Objective-C.
+
+In Objective-C fakes can be created easily using the loose typing at runtime. If you create an object that responds to the same selectors as the one you want to fake you can pass it instead by typecasting it to the original.
+
+In Swift the use of `AnyObject` is discouraged by the compiler, so the use of fudging types doesn't work. Instead, you are better off using a protocol. This means that you can rely on a different object conforming to the same protocol to make test code run differently. It provides a different level of coupling.
+
+For my favourite use case of Fakes, look at the chapter on Network Models, or Testing Delegates.

chapters/en-UK/foundations/stubs_and_mocks.md

@@ -43,14 +43,13 @@ It has three tests, that each test their own expectations.
 - The second ensures that when `popen(["cat", path])` is called, it returns a number of characters greater than `4096`
 - Finally the third one checks an expectation, and if it's wrong, it will faile the test.
 
-
-// ED NOTE: Should this hosted/not hosted live here? prob not
-
 ##### What is the difference between hosted test targets and unhosted
 
 When talking pragmatically, we're really talking about writing tests against apps or libraries. Depending on whether you have dependencies on Cocoa or UIKit, you end up having to make a choice. Hosted, or not hosted.
 
-The terminology has changed recently, a hosted test used to be known as Application Tests, and unhosted was known as Logic Tests. The older terminology gives a better hint at how the tests would be ran. A hosted test is ran inside your application after `application:didFinishLaunchingWithOptions:` has finished. This means there is afully running application context.
+The terminology has changed recently, a hosted test used to be known as Application Tests, and "unhosted" was known as Logic Tests. The older terminology gives a better hint at how the tests would be ran.
+
+A hosted test is ran inside your application after `application:didFinishLaunchingWithOptions:` has finished. This means there is a fully running application, and your tests run with that happening around it. This gives you access to a graphics context, the application's bundle and other useful bits and pieces.
 
 Un-hosted tests are useful if you're testing something very ephemeral/logical and relying only on Foundation, but anything related to UIKit/Cocoa subclasses will eventually require you to host the test bundle in an application. You'll see this come up every now and again when setting up test suites.
 

chapters/en-UK/foundations/stubs_mocks_and_fakes.md

@@ -13,10 +13,10 @@ def create
     rest = readme.split(start_split)[1]
     finale = rest.split(end_split)[1]
 
-    template = start_split + "\n\n| Topics | Last Updated | Length | \n| -------|----|-----|\n"
+    template = start_split + "\n\n| Topic | Last Updated | Length | \n| -------|----|-----|\n"
 
     template = add_markdown_files_to template
-    template += "\nOver 200 words: " + rough_completion_estimate[:covered] + "%"
+    template += "\n\nOver 200 words: " + rough_completion_estimate[:covered] + "%"
     template += "\nOver 300 words: " + rough_completion_estimate[:solid] + "%\n"
 
     new_file = start + template + "\n" + end_split + finale

chapters/en-UK/xctest/testing_terminology.md

@@ -2,19 +2,16 @@
   chapters/en-UK/what_is/what_and_why_of_the_book.md
   chapters/en-UK/what_is/how_can_i_be_pragmatic_with_my_testing.md
 
-  chapters/en-UK/xctest/useful_terminology.md
   chapters/en-UK/xctest/what_is_xctest_how_does_it_work.md
   chapters/en-UK/xctest/types_of_testing.md
   chapters/en-UK/xctest/unit_testing.md
   chapters/en-UK/xctest/behavior_testing.md
   chapters/en-UK/xctest/Three_Types_of_Unit_Tests.md
   chapters/en-UK/xctest/test_driven_development.md
   chapters/en-UK/xctest/integration_testing.md
-  chapters/en-UK/xctest/testing_terminology.md
 
   chapters/en-UK/foundations/dependency_injection.md
-  chapters/en-UK/foundations/stubs_and_mocks.md
-  chapters/en-UK/foundations/fakes__plus_protocols_.md
+  chapters/en-UK/foundations/stubs_mocks_and_fakes.md
 
   chapters/en-UK/oss_libs/expanding_on_bdd_frameworks.md
   chapters/en-UK/oss_libs/mocking_and_stubbing__ocmock_and_ocmockito_.md