but this is not the solution, the idea with route names relating to path is intended. There is no reason that I see that functional tests should break because of the change, unless you are dealing with a project that is not using proper related  paths or hard coded ones. Instead I think what we can be proposing is to lock a route to path test for functional, that locks this definition, if there is a change in any of the route map then it should fire up a warning to update the path on the functional test. no?