Updating environment variables
It is possible that even if you have installed the latest version of Java, your browser may not be able to use it because it is not enabled.
This could happen when you install other applications that also install Java and the vendors do not want to change your browser settings.
To specify a value for an environment variable, use the syntax appropriate for your command processor.
For example, on Windows, you can set the The commands to set environment variables can be executed at your command prompt to take effect immediately, but the settings persist only until you log out.
For example, in the screenshot above we have created a “Dev locally” environment where the variable Web App Url will be replaced by to be used in the second request, you can use test scripts to make your life easier.
The test script runs inside a sandbox and Postman provides the postman object to interact with the main Postman context.
But that convenience wanes when those credentials change often and you need to modify those settings by hand.
Every aspect of your Runscope tests can be accessed via the API, including the ability to create and delete tests, environments and schedules programmatically.
To have the settings take effect each time you log in, use the interface provided by your system or place the appropriate command or commands in a startup file that your command interpreter reads each time it starts.
On Windows, you can set environment variables using the System Control Panel (under Advanced).
If you do end up making a mistake editing your tests or environments, you can always roll back to a previously saved state using Runscope Revision History.
Now that you know how easy it is to make updates to initial variables and other environment settings, you might be wondering if you can embed a PUT call inside one of your tests. But as stated above, proceed with caution—you are, after all, updating a live environment.