Jim Brännlund
Jim Brännlund
Would @audricschiltknecht be interested in the reviving this for v4?
> Hello, I completely forgot about that PR, thanks for reminding me. I had a quick look at the changes for V4, and from my point of view, it's close...
What's the purpose/use case of those directories?
I see. Since (currently) the report is generated, like you said, on first init - I don't think there's a straightforward way of doing this. One approach you could take...
You're welcome @jnunez10010 In v4 (aka next-gen) of this plugin, we actually write the report for each test. There are mainly two reasons for that: - For long running test...
`4.0.0rc1` is out. Question: Should this fixture write a new report "per test" or do you just want to be able to set the path to the report using a...
No harm in adding a fixture, if it's possible without too much work. It will be a Session-scoped fixture in that case.
Maybe @jnunez10010 can clarify why it isn't possible to pass the argument today using command line, pytest.ini or setup.cfg, but would be possible using a fixture?
Why do you need (want) a separate report per test?
It's good you have a workaround as I think this is out-of-scope for this plugin unfortunately.