New issue 287: Fixture finalizer failure causes other finalizers to not be run https://bitbucket.org/hpk42/pytest/issue/287/fixture-finalizer-failure-causes-other
Andreas Pelme: When tearing down fixtures and one finalizer (registered via `request.addfinalizer`) fails (with an uncaught exception or with `pytest.fail`) - no other finalizers will be run. Of course - the fixture finalizer could be fixed to not throw exceptions and the problem would go away. However, I find it useful to be able to make assertions in the fixture teardown. I have a stubbing fixture (similar to pytest's monkeypatch). It checks that the stubbed methods actually was called during the tests, and triggers assertions otherwise. When this happens in one test case, it causes database fixture and all other kinds of failures for all other tests. I am not sure this is a valid use case for fixtures, if not, feel free to close it. :) -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue. _______________________________________________ pytest-commit mailing list pytest-commit@python.org http://mail.python.org/mailman/listinfo/pytest-commit
