[Bug] Assertion error information not showing in Total Requests tab

[EshtechZ]

Describe The Problem
After running the collection through the command line and get generate the HTML extra report,

in that case, the Test name and assertion error is not showing in the Total Requests tab (blank data) as it is showing the same as in the Failed Tests tab.

Steps To Reproduce
Steps to reproduce the behavior:

1. Run the collection having some assertion error.
2. Open the HTML extra report.
3. Navigate to the Total requests tab and check failed test reason under Test Info>> Test Failure section. (Test name and Assertion error is missing here, only able to see reason in Failed Tests Tab header -3)

What Are You Seeing
Test Name & Assertion error is not showing in the Total Requests tab, Test information section as it is showing the same as in the Failed Tests tab.
Navigate to the Total requests tab and check failed test reason under Test Info>> Test Failure section. (which is missing here, only able to see reason in Failed Tests Tab header -3)

Screenshots and Gifs
Please find a screenshot that helps you to reach the issue place.

Collection and Environment Files
Sorry, won't be able to provide you but it's easy to reproduce, you can run any collection having to fail test case (any assertion fail like: response code can be different).

Version and Platform Information:

• Newman Version [5.1.0]
• Newman-reporter-htmlextra Package Version [Not exactly remember, will check and update the version soon but it could be
  latest as I recently installed it, in the same month.]
• OS [Windows 7]

Additional Context
All covered in the above description.

• Are you using the reporter from the command line or with a script? - Command
• Are you using the default template or a custom version?- htmlextra report.
• If you are using a custom .hbs file, please include this in the report.
• Have you made any local changes to the index.js file?

Label
Inside the Total requests tab, it should provide a whole description of pass/fail test cases, if any error comes then it should give at least assertion error message include a reason as it is showing in Failed Tests Tab.

Thanks.

[DannyDainton]

Thanks for reporting this @EshtechZ,

It's not something that happens all the time as more and more people would have reported it so far. 😁

I think it's to do with either having a test, in the request, with the same name twice or having a test with the same name at 2 different levels. 🤔

• Could you check to see where those tests in the collection live? Request, Folder or Collection level?

• Are there 2 test with the same name? "Status code is 200"

You can see on the test results table that it passed and failed at the same time. It's strange that it shows in the failed tests tab though, as the same information is populating that information in the request page. 🤔

[DannyDainton]

@EshtechZ Are you able to provide answers to the 2 questions above please?

[DannyDainton]

I can confirm that it's what I think it is:

pm.test("Status code is 200", function () {
    pm.response.to.have.status(201);
});

pm.test("Status code is 200", function () {
    pm.response.to.have.status(201);
});

Having 2 tests with the same name would show the issue - Until I fix the problem you would need to ensure that each Test has a unique name, that way it would show the failed message in this view. The Failed Test tab would show the correct message as the data is coming from a different place, that was tricky to use on the individual request level.

[EshtechZ]

Hi Danny, Thanks for the quick action. I will check it again and get back to you. Thanks, EshtechZ

…

On Sun, Jul 12, 2020, 5:31 PM Danny Dainton ***@***.***> wrote: I can confirm that it's what I think it is: pm.test("Status code is 200", function () { pm.response.to.have.status(201);}); pm.test("Status code is 200", function () { pm.response.to.have.status(201);}); Having 2 tests with the same name would show the issue - Until I fix the problem you would need to ensure that each Test has a unique name, that way it would show the failed message in this view. The Failed Test tab would show the correct message as the data is coming from a different place, that was tricky to use on the individual request level. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#247 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMMA7PREK7MP4CJSWA3E4PDR3GQYTANCNFSM4OSMO7LQ> .

[EshtechZ]

Hi Danny,

I checked the above scenario and i don't have any duplicate test data or script. Each request has only 1 test script which is fine.

[DannyDainton]

I was able to reproduce this with the tests with the same name, didn't really matter if these were in the same script or at different levels.

There's an issue in Newman with the sendRequest() function used in the app, this would create the same test against that request - Do you have anything like that in the request?

[anhhanuman]

I would like to report the same issue @DannyDainton
Look, the failed tests are not displayed

About my test cases

pm.expect(companyName).to.eql(expectedCompanyName);