I have some tests (maybe not many) and I want to know where the dangerous gaps are before launch. Do a coverage audit, but not a naive line-coverage report. Instead: 1. Inventory my app's routes, endpoints, and critical modules (payments, auth, data writes, permissions). 2. Map which of these have any test coverage at all, and which have none. 3. Rank the uncovered areas by blast radius: what breaks, who notices, and does it cost money or data if it's wrong. 4. Flag coverage that's technically present but useless, like tests that only assert a function returns something, or endpoint tests that only check for a 200 on the happy path. Present the result as a prioritized list: the five to ten test gaps that matter most, with a one-line reason for each and a rough effort estimate. Don't write any tests yet. I want the audit first so I can decide where to spend the effort. And don't pad the list with low-risk gaps to make it look thorough; I care about the places where a bug is expensive. If my project has a coverage tool available, you may run it to inform the analysis, but the deliverable is the prioritized gap list, not a percentage.