Does high Code Coverage mean high test quality?

It's possible to write a test which achieves extremely high code coverage for a system yet contains no assert statements.

We looked at ways of preventing this, and what other measures one should use to ensure the effectiveness of your test suite?

• Code Review should be used to ensure that tests, actually test and are not just propping up the coverage metrics
• Mutation testing, using a tool such as Jester, will also uncover tests which are "weak"
• [Clover2 http://atlassian.com/clover] reports the number of Classes each test actually covered ("per-test coverage") showing potential "power tests" which possibly cover a lot of code that is poorly tested

File:Http://img.skitch.com/20080629-dyr64htmkhifa233a3wu46acka.jpg