Shamasis Bhattacharya
Shamasis Bhattacharya
By the way, let's deep dive the heap issue, it could also be other factors while we speculate summary alone. šš
Interesting. Quick question here ... the writing of file to exported format is done outside the reporters. How about shifting this messaging to there?
Yep. Agreed. This should be addressed. The summary computation should mark failed iteration +1 if any test failed / request failed in that iteration.
@kunagpal - what needs to be changed in runtime for this? can it not be done completely from CLI reporter / summary.js?
I've commented here for @codenirvana and @DannyDainton to give a quick feedback on the summary timing data structure. @adityaofficial10 meanwhile, since this is almost final, can you add the tests...
@adityaofficial10 reviewed it. It's a go from my end. But I want two questions to be answered that I left as comment. You too can chip in your answer to...
I'm talking of this comment https://github.com/postmanlabs/newman/pull/2656#discussion_r594065737 > 1. Is this timings data structure acceptable now? @DannyDainton @codenirvana > 2. Why's there a need to + 1 on the iteration number?...
Iām afraid this is by design. The body is not retained since it can get too big for most cases and cause things to crash. Newman stores report on memory...
Add your console.log to the test script of collection. As such adding one script will make it run for all responses. @luizfzs
> Should I be working on this issue? Is this a priority issue that needs to be fixed? > > @AswinCG2002 i see you are interested in contributing to a...