3 ms·
I like pytest for the ergonomics of its static setup/teardown/fixtures (plus not having to stuff everything into a unittest.TestCase). Unless you mean using gen
by andreareina 6y ago
I like pytest for the ergonomics of its static setup/teardown/fixtures (plus not having to stuff everything into a unittest.TestCase). Unless you mean using generated input in those bits? In which case yeah, not ideal. At $dayjob we do some chonky processing; generating new input for each property we're testing is just barely ok right now, but that's probably not going to hold for very long.
[1] https://github.com/pytest-dev/pytest-subtests https://github.com/pytest-dev/pytest-subtests
- nhgiang 6y agoSorry for not being clear. This is what I was talking about: https://github.com/pytest-dev/pytest/issues/916 https://github.com/pytest-dev/pytest/issues/916 It is a known issue. Basically your fixture/setup/teardown, which you expect should run for every example generated by Hypothesis, actually only run once.
- andreareina 6y agoOh yeah I remember that. Hasn't been an issue for me, thankfully.