HOw to update the environment variable or global variable with collection results when fired with newman command line

1. Newman Version (can be found via newman -v):
2. OS details (type, version, and architecture):
3. Are you using Newman as a library, or via the CLI?
4. Did you encounter this recently, or has this bug always been there:
5. Expected behaviour:
6. Command / script used to run Newman:
7. Sample collection, and auxilliary files (minus the sensitive details):
8. Screenshots (if applicable):

[kunagpal]

@Sripathi1983 There are two parts to handling this:

1. Ensure that environment values are updated to their desired values using postman.setEnvironmentVariable("var_name", "var_value");, or postman.setGlobalVariable in your collection request test scripts, where applicable.

2. To update the environment / globals file, you can use --export-environment / --export-globals, like so:

newman run coll.json -e env.json -g globals.json --export-environment env.json --export-globals globals.json

[kunagpal]

@tegomass You’ll have to use the export options, like so:

newman.run({
    collection: '/path/to/collection.json',
    exportEnvironment: '/path/to/new/file.json',
    exportGlobals: '/path/to/some/other/file.json'
}, function (err, summary) {
   // change the world here...
})