|I don't whine about being sacked, as I said to them, this is the right decision if our view does not fit. I have enough customers to not really care about being sacked.
I know what a unit test is, and I know what an integration one is. But they should not be done "later" or "before" but together, and the two kinds should run after commit anyway.
When people spend more time implementing a mock than doing an actual implementation, then you have a problem. This is what I call "Astronauts", which might be fine if you have deep pocket supporting you.
My metric is test coverage. Either my tests cover stuff, either they don't. That they are covered by a unit test or by a integration one is of no concern, as long as both kind of tests, should be able to run on my dev machine and repeatable.
I am not against mock, I am against people wasting resources writing tests which does not improve coverage.