Markus Unterwaditzer
Markus Unterwaditzer
Generating new first-class tests while the tests are already running will be awkward for the UI, so I think subtests are the only option (for a start only the parent...
I see. The idea was to, as _a workaround_, generate as many testcases as possibly needed for hypothesis, and then just skip the ones that are not needed.
I'm currently fooling around with this. Would it be an OK API if there's a way to instantiate sub-sessions (on the same config)?
No, I meant to actually instantiate a new `_pytest.Session` within the existing test session. Nevermind, it seems to be unnecessary. Meanwhile I've come up with https://gist.github.com/untitaker/49a05d4ea9c426b179e9, the thing works for...
I'm not sure if we can set `nextitem` properly without changes to at least Hypothesis.
Currently it seems that module-level fixtures are set up and torn down for each subtest. I wonder if that's because of the incorrect `nextitem` value.
I'm currently experimenting with this, I fear that this might leak state to subsequent testfuncs in different modules/classes.
I've updated the gist.
BTW should this hack rather go into hypothesis-pytest for trying it out, or do you already want to stabilize an API in pytest?
Also I'd like to hide the generated tests from the UI.