pytest

py.test has a different way of finding tests. It loads Python files starting with "test_" or ending in "_test.py" then uses reflection, to find functions starting with "test_" or classes starting with "Test", or functions marked with the attribute "__test__" (which is applied by the @nose.tools.istest decorator). See https://github.com/pytest-dev/pytest/blob/d69abff2c7de8bc65b... This mechanism of scanning the AST is a different approach and won't find the same set of tests. Scanning the AST can be useful and things like https://macropy3.readthedocs.io/en/latest/ are awesome though!

Sorry for not being clear. This is what I was talking about: 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.

I feel very uncomfortable whenever I read a code-of-conduct, including the PyTest one: https://github.com/pytest-dev/pytest/blob/master/CODE_OF_CON... I don’t think there’s anything wrong at all with the spirit of such documents, but they seem to normalize a world where bad behavior is regulated by well-intentioned ad hoc legalese. In the good old days, one would receive on the spot practical training on how to behave by ones parents, friends, older siblings, teachers etc. I suspect my revulsion at reading codes of conducts is part of me being in denial that there are so many more people in the world now, on the internet, who were raised by the social / etiquette equivalent of animals.