What I didn't hear you mention was peer reviews.
You did say 'we' a lot. So I assume this is a team. The best use of a team is to check that you're not simply deluding yourself about how awesome you are.
Peer review production code. Peer review test code. The best way to see if you have written readable code is to have someone else read it. Let's do better then just keeping the CPU happy.
Also, you seem almost too enthusiastic about code quality. While code quality is certainly a good thing, it's easy to do bad things in it's name. Guard against this by sanity checking. Watch out for tests that take time to create but don't really help you find defects any faster. Watch out for tests that impose a structure on your code (perhaps by digging behind abstractions) and make refactoring harder.
Don't depend too highly on analysis tools either. I'll take the subjective but considered opinion of a human reviewer over what some tools says about readability any day. Use the tools to remind you of things to consider. Do not worship them as gods. They are good tools but poor masters.
And above all. Don't forget that the point is to get a job done.