From 0ae5dd19d5e7256b0876987948774b48e207f231 Mon Sep 17 00:00:00 2001 From: Eliah Kagan Date: Fri, 24 Nov 2023 02:19:56 -0500 Subject: [PATCH] Revert "Treat XPASS status as a test failure" For its immediate goal, this facilitated identifying the XPASS status of TestSubmodule.test_rename and verifying that the revised xfail condition eliminated it. In the test output, XPASS is written as a failure, with strict xfail behavior noted. Contributors less familiar with marking tests xfail may mistake this to mean some behavior of the code under test was broken. So if strict_xfail is to be enabled, it might be best to do that in a pull request devoted to it, and maybe even to add to the docs, about how to recognize and handle newly xpassing tests. This reverts commit 0f8cd4ce4a7f942d793a8670257f8738ab18b757. --- pyproject.toml | 1 - 1 file changed, 1 deletion(-) diff --git a/pyproject.toml b/pyproject.toml index 5c3117096..7109389d7 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -8,7 +8,6 @@ filterwarnings = "ignore::DeprecationWarning" python_files = "test_*.py" tmp_path_retention_policy = "failed" testpaths = "test" # Space separated list of paths from root e.g test tests doc/testing. -xfail_strict = true # Treat the XPASS status as a test failure (unless strict=False is passed). # --cov coverage # --cov-report term # send report to terminal term-missing -> terminal with line numbers html xml # --cov-report term-missing # to terminal with line numbers