There are several variable scopes in Postman. But they are all somehow permanent from view of running requests. If I start a runner to perform some requests there is no possibility to specify or override variable values only for the lifetime of this tests. I have to change either global or environment or collection or local or interaction variables and have to save the global, environment or collection scope or test-script or data file. So the changes are permanent and I have to remember to remove or change back the variable after my test run and if I don’t future test runs will behave different without my awareness.
So I would appreciate a new runner variable scope. Variables of this scope can be specified (or imported from file) within a runners window. These variables exist only for the lifetime of this runner instance and overrides other variables from global, environment and collection scopes when accessed in the request builder via double brace replacement.
This would allow to temporary adjust some settings during a test run without the need to save and withdraw these changes to permanent storage. Or without the need to hold a confusing number of environments to address all issues.