Re: Using refactoring to make code more testable Re: [refactoring] Using refactoring to make code more testable

Michael Charland <[email protected]> wrote:

> Along similar lines, how do i get people to add tests? Most of the people I work 
> with do not add any unit tests when submitting new code or fixing old bugs. It's 
> a pretty generic question, but any approaches would help.

These people who work with you: do they work _for_ you, or _near_ you?  

If the former, obviously, you can command them.  

If the latter, you must convince them.  To do that, start from the basics: why do you believe that tests are worth doing?   If you had to make an "elevator speech" about it, what would you say?  Has your group ever had problems because there were no unit tests?  Are they ignorant or just lazy?   

But now the hardest question:   Do they listen to you in general?  I don't mean _obey_, I mean _listen_: when you speak, do people consider what you're saying?    

If so, present your reasons slowly, gathering agreement one developer at a time.  If not, you've got bigger problems than whether people submit tests.  

Cheers,
Cornelius


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

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/