Zen and the Art of Unit Testing

Re:Zen and the Art of Unit Testing by zamalek on Wednesday March 15, 2017 @08:26AM (#13875588)

> I found that it basically just tightly couples your test to your implementation details

Compilation in strictest form of TDD is the first failing test that you run. Catching this has advantages, such as knowledge and contemplation of altered ABI.

Your interface refactoring could also originate from your tests. Alter the code in your test (even the mock interface) until it is clean at that usage site, and the compile/test run until everything passes.

[ Parent | on HN ]

Re:Zen and the Art of Unit Testing by hamilyon2 on Wednesday March 15, 2017 @01:46PM (#13878141)

This is undesirable in my book. Mere refactoring should just check all boxes in test suite. If I changed tests as well, how would I be sure no functionality changed? Tests did not serve their's purpouse in the end

[ Parent | on HN ]

Re:Zen and the Art of Unit Testing by adrianratnapala on Wednesday March 15, 2017 @02:03PM (#13878295)

This whole discussion has been about an "interface refactoring". I.e. a change to internal interfaces so obviously anything that sees that interface is subject to change.

Now it is true that some interfaces are more stable than others, and you can make a good argument that testing shouldn't be done at boundaries that are likely to be unstable.

[ Parent | on HN ]