Re: Ambiguous Refactoring Solution

On Fri, Sep 25, 2009 at 2:19 PM, Richard <[email protected]> wrote:
>
>
>
> In article <[email protected]>,
>
> Steven Gordon <[email protected]> writes:
>
> > > Or, holy shit batman!, you could test it manually.
> >
> > And possibly miss testing the one corner case that was addressed by that code
>
> ...which you could still miss if you wrote unit tests.


Absolutely true. However, there are at least three big differences.

1) If I miss it in the unit test then the fact that I missed it is
documented by the unit test. When the bug eventually shows up I can go
to the unit test, see that I missed it, and add it.

2) Once it is in the unit test I won't miss it again. With a manual
test I could test something today and forget to test the same thing
tomorrow.

3) Everything that I don't miss today, when I manually test, I will
have to find and manually test tomorrow. According to the Pragmatic
Programmers after the second time I do that if I don't automate it I
am not doing my job as a programmer (You might call that dogma too,
but it makes a lot of sense.)


------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/refactoring/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/refactoring/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/