The current matching system (and any regexp-based matching system in general) can allow you to create routes, and there is no defined behavior for what order the matches will be attempted in (in practice; it's loosely based on whatever order find returns files in).

Some loose heuristic would be to look for all test cases that use the EndpointTestTrait, combine all of their goodUris() into a list, and test for good uris that match against multiple endpoints. This can get really complicated across different request methods today, and would get even more complex should disambiguation across other request variants (e.g. accept headers).