Test Driven Development practitioner (I'm not) would probably sigh (at least) reading this. According to TDD you should first write your failing (obviously) test, and then write the code that would make this test pass. This way, checking that tests are actually doing something is part of the workflow.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.