Are you following TDD or you test your code afterwards?
It depends on the code. If it's something complex I prefer test-first. If not, I'm either not testing at all or testing afterwards.
Test first for bugs. Test after for new features.
It depends on the client. If it is me, write tests first, build the code, test it again, coverage 100% then deliver.
If it is the client, give it to me running and then do what you want with tests.
I like TDD but its a bit difficult to implement Teamwise (Testers + Developers) . i follow test code afterwards
From my experience there are two implementations of TDD.
It takes a long time and a lot of dedication to do the first implementation. Most people (including myself) tend to go with the second one.
Then of course (sadly) one has pressure from the client/project which at times does not allow either of the above.