Any unit tests which are not run as a part of a continuous integration process are worthless.

...or at least nearly worthless. They are like oysters that are never opened. They might have edible meat inside or even be spinning a pearl, but if they are never cracked then they are... I dunno, I guess the oysters could be paperweights. It's like a stock that trades at one percent of its real value. I guess it does have some value, but, well if you're using oysters as paperweights I think no one has showed you what to do with oysters. The continuous integration process should freak out whenever a developer checks in code that breaks a test "embarrassing" the developer and keeping developers from thus sabotaging the code base. Without this crashing behavior developers can just check in code that breaks a test and eventually will and eventually at least some of the written unit tests will break when run standalone. The team will notice too late and eventually become passively numb to the silly tests that provide no value because they haven't worked in three months.