Management has reviewed DevOps which is already being shown to customers and wants to introduce a code coverage metric to show customers how good the code is. Code coverage now has to be 80% or higher across the board, it's been decided by management, and there is no discussion on this topic. The front-end presentation layer has minimal business logic and most of the code that exists is generated objects to shift data to the backend (which in turn mostly shifts it to a 3rd party API that does a lot of the business logic). I now have to write thousands of pointless tests while also being 85% billable to the client.
I think code coverage can be used as a tool, but should not be used as a metric to promote the product.
I suggested an automated e2e test might be better placed to prove that things are working, but have been told we're not going in that direction.
I'm close to writing a code coverage test that uses reflection to touch all of the code, catch all exceptions, and return a positive result.

FUCKING TFS

Morning: Boss decided he was changing all the table names, used a different ORM than we are used to, and implemented it in such a way that the connections stay open and live forever, and had ultimately destroyed half our existing codebase.
Midday: clients keep messaging saying that everything is broken, and rather than accepting that we are fixing it, they want an entire breakdown of exactly what is wrong.
Afternoon: clients still say things are broken even though they have been fixed - they keep sending month old screenshots, which is obvious because the entire interface has changed since then.
Conclusion: shouldn't have gone to work today.