home » snippets » java » testing

Links

• Don't enforce invocation order (Freeman/Pryce p 280). (Does EasyMock allow this?)
  • http://books.google.com/books?id=QJA3dM8Uix0C&lpg=PT154&dq=%22don't%20mock%20types%20you%20can't%20change%22&pg=PT438#v=onepage&q&f=false
• Martin Fowler: Mocks aren't Stubs
• stackoverflow: Value of mock objects and high level unit tests
• Don't mock types that you can't change (or that can change under you) – e.g. for third party stuff.
  • Hard to know if mock behavior is correct. Behavior might change in newer version of library.
  • Write an adapter layer instead and mock that.
  • (Freeman/Pryce - p69)
    • http://books.google.com/books?id=QJA3dM8Uix0C&lpg=PT154&dq=%22don't%20mock%20types%20you%20can't%20change%22&pg=PT154#v=onepage&q=%22don't%20mock%20types%20you%20can't%20change%22&f=false
• Use expect(mock.callmethod(isA(String)) instead of expect(mock.callmethod(“foo&bar”))