Newman library in node.js script: access iterationData value for each iteration cycle

šŸ™‹ Help
,
1

Hello,

I have a node.js script reading data from an inpout CSV file and making request to a 3rd party API. For each iteration of the input data I want to log to the console the values read but can not fine a way to do so? I have looked into the ā€˜argsā€™ content for a number of events and can not find any populated with the data read from the input file?

thanks

2

Hey @guiom

Welcome to the community! :star:

The best way to see whatā€™s happening is to share the script that youā€™re using, itā€™s far easier that trying to describe it :grin:

3

there is nothing to the script really:

the initial section is as follows:

newman
    .run({
        collection: options.collection,
        environment: options.environment,
        iterationData: options.data,
        reporters: "cli",
        verbose: true
    })

I then have a section dealing with the response data from the remote API:

.on('request', function(error, args) {
    if(args.response.json()) {
     write response body to file
    }

}

what I need is to be able to write to the output file the data read from the input CSV and I can not find a way to access the iteration data in any of the events.

4

the input data for example would be:

number
12345
23456
78901
etc.

5

on write the response body to the file I would for example what to prepend the ā€˜numberā€™ value to the line entry

6

This is something that I would use to run the Collection and write the response to a file:

const newman = require('newman'),
      fs = require('fs');

newman.run({
  collection: 'collection.json',
  environment: 'environment.json',
  iterationData: 'data.json'
}).on('request', function (error, args) {
  if (error) { 
    console.error(error)
  } else {
    fs.writeFile('response.json', args.response.stream, function (error) {
      if (error) { console.error(error) }
        console.log(`File Created`)
    })
  }
})

Not sure I follow the part about the iteration data from the CSV as you have that separate to the collection now in the iterationData property.

You might need to explain that flow a little more.

7

thanks and yes that is fine to write the response data to file and essentially how it is done currently.

With regards to the iteration data, you say this is available in the iterationData property. How would you output a console entry with the data (from the iteration data at the current index) being used in the current request?

for sake of argument if my iterationData: ā€˜data.csvā€™ is as follows:

field1,field2
a,b
c,d
e,f
etc.

So effectively 3 iterations of data with 2 values each.

As you write the response stream to file. How would I get the field1 and field2 values that were used in the corresponding request?

8

I tried to answer that here:

The only thing that you would need to change is the way you get the values from the data field during the different iterations:

let fieldOne = pm.iterationData.get('field1'),
    fieldTwo = pm.iterationData.get('field2');

console.log(`\n${fieldOne},${fieldTwo}`)
1 Like
9

ah great thanks. I seem to be getting ā€œReferenceError: pm is not definedā€ and presumably need to reference it elsewhere in the script for this to work. Obviously within say a Postman pre-request script and environment it is defined, but how to do this within a node.js script?
"

10

Hmmā€¦thatā€™s odd. Which version of Postman are you using?

It just needs to be in the Collection in the places that I mentioned - As in, the code above needs to go in the Pre-request Script.

You donā€™t need to do anything in the node script apart from adding the .on('console') part from the linked thread.

1 Like
11

ah ok fine I get it and many thanks.

this works fine, still its a bit hacky :wink: I would have thought that accessing the iteration data directly from the events in a node.js script would be quite a common requirements. In the same way that saving the response body to file directly from Postman is quite an obvious requirement.

Many thanks for your help, prompt response and so on. This is much appreciated

2 Likes
12

If youā€™re using the datafile with Newman, you would have it stored somewhere in the first place.

newman.run({
  iterationData: 'data.json'
})

Itā€™s hacky because it feels like, a round the houses way of getting the data via the Collection run, that you already have available before the run. :smiley:

There is an option to Send and Download the response body to a file when sending individual requests but itā€™s not part of the Collection Runner.

All feature requests can be added here though:

13

ok let me explain further and maybe it will make sense.

the input file is a number, say a telephone number. this number is used to query a data source which returns a response body with some data related to the number. It does not however echo back the number itself. So to write the number to file together with the response body I need to access to iterationData as the request is made. It works via preRequest scripts and the on console event as we discussed above.

The data is indeed in the options for the Newman run

newman.run({
       iterationData: 'data.json'
})

I dont know if this iterationData can be accessed in the events which is why I have to go via the console at the moment. There is possibly a better way but I havent found it so far.

2 Likes
14

Hello gulom, Iā€™m trying to achieve the same thing. You can get the iteration index from the args value as follows:

.on('request', function(error, args) {
    var indexOfIterationDataFileLine = args.cursor.iteration;
    ...
}

You can then use that index to look up the line in your data file, be it CSV or JSON.

1 Like
15

So there is no proper way to get current iterationDate using newman API, right?

1 Like