Unable to skip specific request (folder) to generate htmlextra report

[Escape147]

Is There An Existing Issue

• I have searched the issue tracker for similar problems.

What Are You Seeing

When the --reporter-htmlextra-skipRequests (--reporter-htmlextra-skipFolders) parameter is used to run the command, the number of Skipped Tests in the generated report is 0

Steps To Reproduce The Issue

1. Run Newman using the command in the terminal
2. Open the new htmlextra report in a browser window
3. Click on the 'Skipped Tests' tab
4. No statistics requested

Full Newman Command Or Node Script

Command1：newman run Test-skip.postman_collection.json -e Test.postman_environment.json -r htmlextra --reporter-htmlextra-skipRequests "request name with InvalidParameterException"
Command2：newman run Test-skip.postman_collection.json -e Test.postman_environment.json -r htmlextra --reporter-htmlextra-skipFolders "folder name with Error code"

HTMLEXTRA Version

1.22.11

Newman Version

5.3.2

Additional Context

[github-actions]

Hey @Escape147: 👋 - Thanks for helping to make the reporter better by raising this ticket. I will take a look as soon as I can and get back to you. Cheers, Danny.

[DannyDainton]

Hey @Escape147,

That flag only relates to what is displayed in the final report:

The Skipped Tests section relates to any tests that you have within your Collection file that use the pm.test.skip option.

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

[Escape147]

@DannyDainton

• Thank you very much for your reply, I have solved the problem. Want to know what the final report in your description refers to?
  

[DannyDainton]

The final report that's created. There's only 1 report that gets created but that could be displaying anything based on flags that might be used.

[DannyDainton]

If you solved the problem and you no longer have an issue - Can we close this out?

There isn't anything that I'll be changing on my side for this.

[Escape147]

Mmm Good

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.