Standard macros seem to be using test_runner::contextualize_config everywhere. This particular function will fetch environment variables for config values and override them when correct value is found. As a result, value deduction order is environment variable, then custom value, then default value. Though, the usual order for configuration values in many cases is custom value, then environment variable, then default one, because individual case usually "knows better" what value to use.
Standard macros seem to be using
test_runner::contextualize_configeverywhere. This particular function will fetch environment variables for config values and override them when correct value is found. As a result, value deduction order is environment variable, then custom value, then default value. Though, the usual order for configuration values in many cases is custom value, then environment variable, then default one, because individual case usually "knows better" what value to use.Any thoughts?