Are Python flask order of routes defined?

I have a setup similar to the below in my views:

@app.route("/test")
def test():
    ...
@app.route("/<to>")
def page(to):
    ...

It seems that function test in the example always will be called when accessing the "/test" url. This is also what I want. But I cannot find this behavior in the documentation. Is it so that a defined name is always prioritized over a variable? Or is it the order of the definitions that counts? Can i set priorities in any way to make sure this will not break in the future?

Flask uses Werkzeug to handle routing, and it orders routes based on how many variable parts are in the route.

/test has no variable parts, while /<to> does, so it'll try to match /test first.

Currently, ordering is done based on the Rule.build_compare_key() function, documented as:

def build_compare_key(self) -> tuple[int, int, int]:
    """The build compare key for sorting.

    :internal:
    """

and returns a tuple of 3 integers:

• 1 if this is an alias, 0 otherwise
• the negated length of the rule arguments
• the negated number of default values for the arguments

This sorts aliases last, then within each group (non-aliases and aliases) puts rules with fewer arguments before rules with more arguments, and finally, for rules with the same number of arguments, puts rules with fewer defaults before rules with more defaults.