Ah I see, you're right. In that case, maybe we should just normalize in the `_onMatcherMatch()` function before calling the `onTestFound` callback then.

That puts this normalization closer to the source for anyone else who ever winds up using `TestRunner.findTestPathsMatching`