> it's not realistic to enforce unit test coverage % with a project at the scale of OpenSSL, right? Why not? You can enforce that all new files should be cove

> it's not realistic to enforce unit test coverage % with a project at the scale of OpenSSL, right? Why not? You can enforce that all new files should be covered (at the very least line-covered). It requires some setup effort (collecting code coverage and either sending it to a tool which perform the correlation or correlating yourself), but once that's done... it does its thing. Then you can work on increasing coverage for existing files, and ratcheting requirements.