RE: Using refactoring to make code more testable

Does the code already do what it is supposed to do?

Kind of, the code is still changing for bug fixes and new features.


Do you know what the code is really supposed to do?
Too much, yes I have a general idea, but every class or line no.

To: [email protected]
From: [email protected]
Date: Sun, 11 Oct 2009 11:08:30 -0700
Subject: Re: [refactoring] Using refactoring to make code more testable















 




    
                  Does the code already do what it is supposed to do?



Do you know what the code is really supposed to do?



On Sun, Oct 11, 2009 at 10:03 AM,  <[email protected]> wrote:

> Oops ment to save this as a draft. I have largish code base (roughly 10 million lines) that my company deals with and a much smaller code base (roughly 250 thousand lines) my team deals with. Currently there is no unit test coverage of any of the code. And the code was not wrote to be tested. My main task is to get the code covered.  I was wondering what kind of refactoring strategies would help make this goal attainable?

>

> Thanks everyone.



 

      

    
    
	
	
	
	


	


	
	 		 	   		  
_________________________________________________________________
New! Get to Messenger faster: Sign-in here now!
http://go.microsoft.com/?linkid=9677407

[Non-text portions of this message have been removed]



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

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/