Very much agree with "sprinkle TDD around for a high ROI" This requires both developer expertise and trust from stakeholders.

But, VeryBigHugeBankCo requires me to have 70% unit-test coverage for 'new' code, as measured by Sonar or whatever, or else I am simply not able to deploy my change to PROD.

So here I am refactoring a DAO, using strategy pattern and functional interfaces, so that I can cover my DB interactions adequately for that 70% metric.

No, I can't just use H2 DB, as the SQL is Oracle-specific.

Yes, there is very little actual value in the new refactor, except to check the box.

This is how we do...