Mocking

[mattagape]

1. The links on this page don't activate as hyperlinks...the same Travis problem as earlier? I can't select any text on this page either.

2. I don't think the Recording calls with mock section explains things properly. e.g. what is the side-effect part doing and why does function() throw an error?

3. What's going on with MagicMock() - MagicMock()? It's not clear.

[ageorgou]

• Using mocks to model test resources:
  • We could also mention that we want to mock processes that take a lot of time/resources, so that our tests are fast and cheap and can be run often
  • Will we have to replace this call to the Google API (and throughout the page) with another map API, or can we still use it (see problem in Issues with "An example Python data analysis notebook" page #58)?
  • (after map plot) "We can do this by mocking the request object": we're not really mocking an object; I'd say we're mocking the Google server.
• The output cell after the patching is very long and does not scroll (same as in "Collaboration" page #79). Does this have something to do with the page not displaying correctly (no clicking or selecting)?
• Testing functions that call other functions:
  • Formatting (mostly spaces around =)
  • I agree that this part is not clear. Perhaps we can say that the MagicMock is a more powerful mocking object that supports more operations?