Re: [pytest-dev] junitxml incremental output writing

2020-04-08 Thread Floris Bruynooghe
On Tue 07 Apr 2020 at 06:46 +0200, Ronny Pfannschmidt wrote: > instead of creating the junitxml report direcly, > one could use the new reportlog plugin, and add report replay to it, > thus collecting the report logs on the first run, then combiningthe > pytest reports to junitxml on the second r

Re: [pytest-dev] What's the best way of writing tests for terminal width resize behaviour in an assertrepr plugin?

2020-04-08 Thread Floris Bruynooghe
Hi Harry, To the best of my knowledge you stumbled into a hard and dark corner of pytest. IIRC previous attempts at improving this have not gone too well. But like this always goes, it sounds like you've set yourself up to be the expert now and are in a great position to clean this up and make i

Re: [pytest-dev] What's the best way of writing tests for terminal width resize behaviour in an assertrepr plugin?

2020-04-08 Thread Zach Kanzler
I wrote an icdiff-based pretty diffs pytest plugin for internal use, and ran into the same issue. I ended up grabbing the terminal width at module-level, as well. I think I went spelunking in the GH issues and found a glimmer of possibility in the notion that get_terminal_width() returns incorrect