i'm glad it doesn't happen just to me. Martin Fowler(!) writes of the disrepair that his tests fall into once he and his team leave a system in the hands of a client. i have had the same experience many times. in fact, one of those times is the reason i always put quotes on "architect."
this "architect" created a fairly buggy, lousy, hack-ridden "framework" that my team and i were required to use, even though i had already written my own framework that was actually better (and somewhat tested). on this project, a couple of us started writing tests, especially around our function buckets designed to eliminate some of the bugs in the "framework." turn around and the "architect" had deleted all the tests. when pressed, he removed them because he didn't know what purpose they served and they didn't compile. i fell prey to the same fault that MF did: i didn't teach my "architect" the value of the tests.
how do you convince someone with yonks of "experience" that they suck at what they do?