52ece0a08dc57267f42ab690564d510738f55427
test-doubles.md
... | ... | @@ -295,6 +295,13 @@ describe Converter, "delegation to logger" do |
295 | 295 | end |
296 | 296 | ``` |
297 | 297 | |
298 | + |
|
299 | +### Other topics to add |
|
300 | + |
|
301 | +* Metz's method for verifying that an object conforms to an interface |
|
302 | +* RSpec's "behaves like" pattern |
|
303 | +* Fixtures |
|
304 | + |
|
298 | 305 | ### Terms |
299 | 306 | |
300 | 307 | * SUT - System under test |
... | ... | @@ -305,8 +312,3 @@ end |
305 | 312 | * "Test Spies" or "Mocking" for Indirect Output - By "indirect output," we mean the calls the SUT makes to DOCs. Example: the SUT makes calls to a logger. We want to ensure that the DOC is getting called properly. |
306 | 313 | * Procedural Behavior Verification. We want to capture the calls to the DOC during SUT execution and see what happens. This means installing a Test Spy. It receives the calls and records them; then afterwards we make assertions on what is recorded in the Spy. What to check indirect outputs? We say that that happens at an "observation point" (e.g., 137). |
307 | 314 | * Expected Behavior. We install a Mock Object, and say in advance what we expect. If the Mock doesn't get what we expect, it fails the test. |
308 | - |
|
309 | -Other topics: |
|
310 | - |
|
311 | -* The four-phase test. |
|
312 | -* Fixtures. |
|
... | ... | \ No newline at end of file |