For projects of any meaningful scale, issues of configuration management kick in very quickly, this is something for which simple tools, rather than programmer convention, should be employed to handle the details. Testing is typically under tooled. The most mature organizations I encounter have some form of automated regression testing that relieves the burden upon the individual developer, and furthermore serves as a stabilizing influence as a project unfolds. Other tools such as browsers, intelligent debuggers, and metrics tools all have a role to play as a project grows. My advice is that given a tedious, repetitive development activity, I'd much rather buy or create a tool that does it for me, rather then spend precious developer hours having to do it by hand.
Developers are a far more precious commodity than tools.
Unfortunately, I do find some organizations have an easier time procuring new developers rather than necessary tools. The dark side of tools is that underdeveloped organizations tend to find sort of a moral anchor in the form of some really cool tool. Perhaps finding some of their development efforts floundering, like a drowning man, they will grasp at whatever tool happens to float, only to find that faith in any one technical tool will indeed drag them down. Trying to apply a technical solution to a nontechnical problem always has a way of turning on you. The lesson here is to never let your project get intoxicated with any in-vogue commercial tool or trend.