-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] The final reports are slow to render #428
Comments
Hey @canle1404: 👋 - 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. |
Hey, @canle1404, Apologies for the tarde response here - It's been a busy time. This is an ongoing issue , one that's been reported a few times. I haven't made any huge changes to speed this up. There are a number of flags that you can use to reduce the amount of information that's part of the final report. Do you need all the information for every single request, who is the report for? Do they need to see everything? There isn't really anything that i'm going to be doing here in the short term, you can leave this issue open for tracking purposes if you'd like to see any progress made in the future though. |
Thank you @DannyDainton |
Is There An Existing Issue
What Are You Seeing
I understand that the size of the HTML report file is larger when using 'newman-reporter-html'. In order to improve its load time, I push it to S3 with Cloudfront. While this method does make it faster, it takes a long time to render (I'm not exactly sure what the correct term is) which causes my browser to slow down for about 1-2 minutes.
Steps To Reproduce The Issue
Generate with the below script
Full Newman Command Or Node Script
newman run \ postman_collection.json \ --environment postman_environment.json \ --reporters htmlextra \ --reporter-htmlextra-export "$REPORT_FILE" \ --reporter-htmlextra-noSyntaxHightlighting \ --suppress-exit-code
HTMLEXTRA Version
1.23.0
Newman Version
6.1.0
Additional Context
No response
The text was updated successfully, but these errors were encountered: