Browse by Tags
All Tags »
test-driven dev... »
TDD (RSS)
Summary Motley: I can't mock something that I have no control over (like third-party or old legacy code) Maven: Design to interfaces, create a wrapper, and use tools for mocking. These are all great practices for leveraging mock objects. ______________________________
Read More...
Summary Motley: Refactoring keeps my design clean from the start, so no more up-front design! Maven: Up-front design is still necessary to achieve clarity on the overall approach (preventing rework later) and needs to be documented to allow others to
Read More...
Summary Motley: To get high code coverage, we should be testing both public and private methods Maven: Only test public methods. Testing private methods gets in the way of refactoring ______________________________ [Context: Maven checks in on Motley's
Read More...
Summary Motley: Refactoring takes too much time - I have to ship you know! Maven: Refactoring leads to much more maintainable code, and if you have tests in place, the return on investment far outweighs the cost. ______________________________ [Context:
Read More...
Summary Motley: Tests need to validate code that has already been written - not the other way around. Maven: Writing tests before you code allows the tests to drive your code while providing more sound requirements validation. ______________________________
Read More...
Summary Motley: You can't possibly write tests before code - there's nothing to test. Maven: Writing tests for a method before coding it has all kinds of design advantages. ______________________________ [Context: Motley has been writing unit tests for
Read More...
