Opening report is slow when it contains long logs

[Wramberg]

I have some test runs that generate a lot of log entries. When opening the report is seems my browser is spending a lot of time presenting all these entries which are immediately collapsed right after.

If I change the behavior to have everything collapsed by default I can open/render the html report much faster.

What I have tested is essentially the same as adding a "collapsed" class here https://github.com/pytest-dev/pytest-html/blob/master/pytest_html/plugin.py#L140

I have no idea if this breaks other use-cases or if other changes are necessary. I also realize that everything related to the collapse functionality is currently in js. Regardless, if something could be done to generate everything collapsed and open the necessary stuff afterwards I believe performance would be a lot better.

Edit: I should mention I use self-contained reports.

[fpiccione]

@Wramberg maybe this will work ?

[Wramberg]

@fpiccione Yes it will. But my issue is about having to make a manual hack.

[BeyondEvil]

Would this help: #168 @Wramberg

[Wramberg]

@BeyondEvil I dont think so. It seems to change which rows are collapsed but not the fact that ALL rows are rendered as non-collapsed just to be collapsed later by javascript. If we instead rendered the passed rows collapsed the rendering would be a lot faster.

[BeyondEvil]

@Wramberg Ah, I see.

How would you like to see this accomplished? INI-file (pytest.ini etc) setting?

[Wramberg]

I imagine it can simply be changed permanently. I do not see this breaking anything since it would not change the final rendered page, just the way it is rendered - but perhaps I am missing something ?

Regardless a command line option or INI setting would be fine for me.

[BeyondEvil]

Even tho it wouldn't technically break something, I'm reluctant to change a behaviour going back multiple years.

Happy to add an INI setting however.

[Wramberg]

I understand. Whichever approach you prefer 👍

[BeyondEvil]

Hey @Wramberg

Would you mind perf-testing my PR?

[Wramberg]

@BeyondEvil Sure. I will check it out tomorrow.

[BeyondEvil]

I merged it. But please feel free to use master branch. Good to have a test before I do a release. @Wramberg

[Wramberg]

Alright will do

[Wramberg]

Alright will do

@BeyondEvil see my reply on your PR #267.