Re: Re: Single assert / Single mock rule in practice

Sometimes I have test-driven a class, and then I can refactor the "private parts" of the class until it is almost entirely different than the original code, but the tests haven't changed. There may be 4 small classes where there was only one large one, it might have been changed to use/not use a database, etc.

On 2014 Jan 15, at 9:03 AM, Mateusz Łoskot <[email protected]> wrote:

> So unit tests (or, as I now prefer, micro-tests) are around implementation, but not around the implementation of the precise thing you are testing. Unit tests, after all, test that the intent of the programmer is satisfied and the intent of the programmer has a lot to do with internals.


--
C. Keith Ray
* (650) 539-4729
* https://www.dropbox.com/s/mpoefyt9bz1yoxx/keith_ray_resume.pdf
* http://agilesolutionspace.blogspot.com/