Issues with using newman-html-extra combined with Contents fields with multiple entries

[yossarian123]

I have the newman task set up:

1. File type
2. pointing to a collection folder on a repo
3. we want to run all collections matching 2 patterns (see screenshot)
4. htmlextra enabled. A directory is specified for the html extra output (Reporter Html Export)

when all of these are configured, then there are not any html extra reports generated and saved at the directory location. This problem is not seen if using URL collection type. The "workaround" for this is to specify an actual html file path in the (Reporter Html Export) field. But since we specified multiple collections that single file will be overwritten by the last collection that you ran.

[carlowahlstedt]

I'm honestly completely unfamiliar with the Newman Reporter htmlextra npm package. Have you verified that using it from the command line without Azure DevOps will get the results you expect? It seems possible that this might be a limitation of that package if it works for a url but not a file. I did a quick review of the issues in that repo but didn't see anything that jumped at me. I did noticed this listed in the readme, which sounds similar:

The default filename, if you do not supply the export location, is now includes the collection name in the filename rather that the reporter name.

Does any of that help?

[DannyDainton]

If you specify an export file name, it will create 2 files of the same name - so the second one will overwrite the first one.

You can add a timestamp to the filename which would make it unique and not create the same thing twice or use the default export path, which will create a filename with the collection name + a timestamp.

Happy to talk about this more on the reporters repo. 😁