Testing on the Toilet: Testing State vs. Testing Interactions

At my workplace there's an ongoing discussion about testing guidelines. People can't agree on what unit tests should do (use mocks or real objects) References we use to gather arguments - http://googletesting.blogspot.be/2013/05/testing-on-toilet-dont-overuse-mocks.html - http://googletesting.blogspot.be/2013/03/testing-on-toilet-testing-state-vs.html - http://blog.8thlight.com/uncle-bob/2014/05/10/WhenToMock.html - http://www.thoughtworks.com/insights/blog/mockists-are-dead-long-live-classicists - http://www.slideshare.net/davidvoelkel/mockist-vs-classicists-tdd - https://dzone.com/articles/single-responsibility - http://martinfowler.com/articles/mocksArentStubs.html#TheDifferenceBetweenMocksAndStubs - http://ronjeffries.com/articles/015-11/tdd-mocks/ - http://www.growing-object-oriented-software.com/ - http://blog.thecodewhisperer.com/2013/11/23/beyond-mock-objects/ P.S. our stack is SQL + DDD + JAVA + J2EE + REST + JSON + HAL + Angular