Newman HTML report error with pm.sendRequest

[tiaden]

Postman for Windows
Version 5.3.2
Win 7 / x64
Newman 3.8.3

1. Create a Post request in Postman native client
2. Inside the tests tab of this post request, make a Get request using PM.sendRequests (example below)

// Read if AMT has the posted values
const randomDataRequest = {
url: 'http://{{domain}}/rh/amts/' + jsonData.id,
method: 'GET'
};

pm.sendRequest(randomDataRequest, function(err, res) {
if (err) {
console.log(err);
}
pm.test('Verify that POST values = GET values', function() {
pm.expect(res).to.have.property('code', 200);
pm.expect(res.json()).to.deep.equal(jsonData);
});
});
// Read if AMT has the posted values
const randomDataRequest = {
url: 'http://{{domain}}/rh/amts/' + jsonData.id,
method: 'GET'
};

pm.sendRequest(randomDataRequest, function(err, res) {
if (err) {
console.log(err);
}
pm.test('Verify that POST values = GET values', function() {
pm.expect(res).to.have.property('code', 200);
pm.expect(res.json()).to.deep.equal(jsonData);
});
});

3. Generate a report using Newman and you will see two requests having a GET request on them instead on one with a POST method

newman-report-issue.docx

[kunagpal]

@zodikadem This is a known issue, as reporters do not support pm.sendRequest just yet. We'll be taking a look at including this in the weeks to come. In the meantime, this issue can be left open for tracking. Thanks for reporting this! 😄

[tiaden]

@kunagpal,
Thank you for the quick reply. I was on vacation, therefore unable to reply.
It was my pleasure to report this. Can we please expect this to be fixed in the next release ? and when that release be ?

[tiaden]

@kunagpal,
Any chances to see this fixed soon ?

[kunagpal]

@zodikadem Unfortunately, I can't offer an E.T.A for this at the moment. I'll update this thread when a fix is being worked on. 😞

[tiaden]

@kunagpal, thank you for the response. I understand.

[MarcosEllys]

Hello, unfortunately this bug continue, is there are some date to fix this problem?

[parinapatel]

@kunagpal Is there any workaround for this bug? Or ETA when it will be fixed ?

[arninio123]

@kunagpal Any update yet? :)

[MarcosEllys]

@kunagpal Any update yet?

[tiaden]

@kunagpal, it is been more than 6 months since I reported this issue. Any plans on fixing it ?
if not, please let us know.

[tegomass]

+1 :D

[MarcosEllys]

@kunagpal Any update yet?

[zankhanarana9]

Any update on this?

[musanas]

+1 for this

[ejerskov]

+1
Any update?
At the moment my html reports are useless because the pm.sendRequest (for test verification) overrides the original request in the report.

[shamasis]

We just moved the reporter out of newman. PR welcome on this https://github.com/postmanlabs/newman-reporter-html

We are also trying to schedule it in the task list.

[ghost]

Hi,

Please note that this is not HTML reporter issue. This is also the case e.g. for junit reporter (tested on 4.10). Here is what I get in junit report:

  <testsuite name="by funding token / user / Add ACH token" id="2b9e6822-a526-4f69-bad8-517ed5646ede" tests="1" failures="0" errors="0" time="0.933">
    <testcase name="FS044 Get fee for ACH token (user) - Response is ok" time="0.933"/>
  </testsuite>
  <testsuite/>
  <testsuite name="by funding token / authorized user / Add credit card token" id="f7b9fe8d-0113-4dfd-afc0-a0d2634e5835" tests="1" failures="0" errors="0" time="0.854">
    <testcase name="FS047 Get fee for Credit card token (authorized user) - Response is ok" time="0.854"/>
  </testsuite>

Because of this empty testsuite xunit plugin in Jenkins fails to generate trend.

So I would consider this as a high priority item on reporters.

P.S. Should we close #1671 and #1631 as duplicates of this one?

[JohnnyBarry]

+1
Any update?
We are also having this issue with both HTML and Junit reporters.

[shamasis]

@codenirvana @kunagpal - this issue is manifesting in various forms in all reporters. Let’s consolidate them in one issue, close the rest and schedule a fix.

[TingYu-Lee]

I still hava same problem about sendRequest() & HTML-reporter
in Newman v4.4.1

[prshntsingh2010]

I am still facing this issue.

[LalithVigneshS]

+1

[RobHalperin]

I ran into this issue today as well. Hoping this gets a resolution.

Also, in anyone else facing this challenge has found an alternative Reporting solution that is free, please let me know. This is very frustrating.

[Shivansh2407]

Can I work on this @zodikadem ?? I would love to fix this as a GSoC Participant

[tiaden]

Sure @Shivansh2407 it's yours !

[DannyDainton]

Hey @shamasis / @codenirvana

Are we going to tackle this issue with sendRequest() soon, it's impacting the output on all the reporters and I would love to see it finally solved :D

I'm crossing the HTML Reporter streams here but here a basic output from htmlextra, which I'm guessing would be the same for this one:

The main request is a POST and within that is the GET - In the report, it's outputting the details of the GET, which was the sendRequest() rather than what was added to the main URL request. :( It's also doubling up on the tests too 😢

[DannyDainton]

@codenirvana Could we transfer this issue to the Newman repo?

[RCarlosx]

Any update about this?

[tarasbulbiak]

Hi guys! This issue was opened more than 3 years ago, is there any updates about the fix?
Thanks)

[eya62]

Hello,
I am still facing same issue.
I am using pm.sendrequest within a test collection.
When using Newman, it is retuning the requests in pre-requests instead of the main Requests.

Any fixes or alternative workarounds for this issue please?!

[vbisbest]

I am actually seeing the main request twice instead of pre-request/main request. How many more years until this is resolved?

[saiudayakella]

@shamasis @shubhbhargav @codenirvana - Any plans to fix this reporter issue? This is blocking us to consume the stats present in the report

Below ticket is also related
DannyDainton/newman-reporter-htmlextra#241

[akyoldas]

Hey, is there any update on this? This bug is affecting newman outputs very badly!

[FahadRS]

Is there any update on this issue?