https://www.youtube.com/watch?v=Xu5EhKVZdV8at 10 minutes you should share your mocks.
At 1330 used full system tests, like selenium, to test user stories.
At 1715 they still have assertions on their mocks but they are extra ticket to the mocks. In other words they use the term mocks to mean fake, not the traditional Mock terminology.
How flexible he could are underlying implementation change without us having to change our test? At 1815
talk-stop-mocking-start-testing-google-code-devs#free-function1 At 22:30 he talks about extracting a free function, a pure function, and how it aids in testing. talk-stop-mocking-start-testing-google-code-devs#free-function1
At 2615, the bad tests, where many things are mocked, actually end up costing you time.
At maybe 28, they talk about what should become a required construction parameter.
talk-stop-mocking-start-testing-google-code-devs#small-amounts-of-untestable-code1 At 32:45 this is correct by visual inspection and code review. OK for six lines of untestable code talk-stop-mocking-start-testing-google-code-devs#small-amounts-of-untestable-code1
talk-stop-mocking-start-testing-google-code-devs#mock-as-last-resort1 At 34:00 Mock as a tool of last resort. Use when dealing with third-party APIs and you have no other choice, for example. talk-stop-mocking-start-testing-google-code-devs#mock-as-last-resort1