You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on May 13, 2025. It is now read-only.
pytest provides a nice framework for skipping tests. It can handle conditionals, expected failures, and much more: http://pytest.org/latest/skipping.html
The system relies on devs decorating tests consistently with pytest.mark subclasses. They suggest:
For larger test suites it’s usually a good idea to have one file where you define the markers which you then consistently apply throughout your test suite.
We should set up such a file for ourselves. At the minimum it should have a standard way of marking tests as "excluded" so we can quickly disable them. (There's even frameworks for rerunning flaky tests automatically: https://github.com/box/flaky)