Each unit test not ending with an assertion is essentially a hack to locally silence your coverage tool, without actually improving the quality of your test sui

Each unit test not ending with an assertion is essentially a hack to locally silence your coverage tool, without actually improving the quality of your test suite. I call these tests "crash-tests", as a crash is nearly the only thing that they can detect. Crash-tests are indeed what you get if your devs are aiming at a high-coverage number without understanding the rationale behind code coverage.