enable `xfail_strict=True` - and stop using `@pytest.mark.xfail` for flaky tests
Open
tests
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 778
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 3
Description
currently the general policy is to apply `@pytest.mark.xfail` to a flaky test that cannot be debugged. Unlike a skip the test is actually run, this test then contributes coverage that isn't actually valid
Contributor guide
Assessment
This issue has not been assessed yet.