Re: Ambiguous Refactoring Solution

On Thu, Sep 24, 2009 at 3:38 PM, Richard <[email protected]> wrote:
>
>
>
> Some examples of where judgment comes into play:
>
> - Do you write unit tests for property accessors?
>
> Without it, you won't have "100% code coverage", but to write tests
> for property accessors that simply return the value of backing store
> is silly.

Really?

Only if there are property accessors which are not being used by any
client code that is unit tested.  In those cases, why implement those
property accessors?


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

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/