Adrian poses the test-question for the real value of unit testing.

There was no hesitation on my mind: "grab those tests" (even if that means you loose that code). Some argumentation and association:

• (Executable) Test (-scenario')s contain the formal interpretation of the informal requirements or expected features. Delving through the nuance of written text, cutting the knots and making the decissions is in there, and that *is* the time consuming part.
• I even associate it to some personal interpretation of cluetrain: true invention is not in formulating the answers, but in asking the right questions. (Well cluetrain would probably just state that you have to be out there, listening to the questions. And associating even further: IMHO the hard-core anti-pattent guys pretty much chant a variation of that same theme.)
• Finally: Good code never stays around anyway: it has to be changed and lived through. Good code happily accepts to be replaced by better code.