testing - Adoption of TDD on older Java application -


i've got problem , i'm asking help

i've started working on web application, has no tests, based on spring 2.5 , hibernate 3.2, not modularized, classes having 5k lines, view technology there jsp used on place quite lot things duplicated (like many similar search forms few differencies not many shared parts).

aplication works well, however, running fine, when there need add or change functionality, realy slow , not convenient.

is there possibility employ tdd @ point? or recomend dont't think can develop forever way now, getting messier time.

thanky answers.

i start picking copy of michael feathers' book working legacy code - pure gold.

once learn techniques refactoring , breaking apart application @ it's logical seams, can work on integrating tdd in newer modules/sprout classes , methods, etc.

case in point, switched tdd approach ten year old application written in every version of our framework, , while we're still struggling pieces, we've made sure of our new work abstracted out, , of new code under test.

so absolutely doable - bit more challenging, , book above can tremendous in getting started.


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -