In a well-tested project, coverage would be ideal, but with some untested obsolete code, I don't think there is a magic tool.
You can write a great test by loading all pages and running coverage to get some guidance.
Cowboy style:
If this is not some kind of critical code, and you are sure that it is not used (i.e. does not process payments, etc.). Comment on this, make sure the tests pass, deploy, and wait a week or so before deleting them specifically (or returning them if you received a notification).
source share