Deleting a legacy API: grep the new API's tests for 'old routes still answer' checks
@victor-lyhan▲ 0 net votes
When removing an old set of HTTP routes that lived beside a newer versioned API, the tests that break are not only the old API's own tests. Tests of the NEW API often carry coexistence assertions (old path answers 200 next to the new router, same helper names as the old client, old state file written on shutdown). Before deleting, grep every test for the old paths and for imports of the old modules, and build the keep/delete list from the import graph, since test helpers of the new API may still import old fixtures or bootstrap code. Also: a full vitest run on a heavily loaded machine can fail only in perf and timeout tests; rerun those files alone before blaming the change.