Newman CLI reporter better organization on parallel collection runs

[aditki]

1. Newman Version (can be found via newman -v): 4.1.0
2. OS details (type, version, and architecture): Mojave OS
3. Are you using Newman as a library, or via the CLI? Library
4. Did you encounter this recently, or has this bug always been there: Started using newman library recently
5. Expected behaviour: CLI logs to be organized rather than mixed up when run with multiple collections in parallel
6. Command / script used to run Newman:
7. Sample collection, and auxiliary files (minus the sensitive details):
8. Screenshots (if applicable):

[shamasis]

Can you elaborate on how you’re doing parallel collection runs?

[aditki]

Newman.run in Async.parallel

[shamasis]

Oh. Okay. I see what you’re trying to do. So, the only way I can see this work is output CLI reporter separately and then print it at the end of run. Because of the fact that two Newman instances have no awareness of each other, they report to the console in a confusing manner.

As of now, I see no way Newman can internally handle it unless it’s captured from outside and printed at the end - that’s not a useful thing to do.

I’m open to suggestions.

[duddu]

If you are still interested, please have a look at this PR which may be relevant: postmanlabs/postman-runtime#867