From 906de71858ae37ab60bd447a3141e7bb49d38a32 Mon Sep 17 00:00:00 2001 From: Sviatoslav Sydorenko Date: Wed, 16 Dec 2020 17:17:57 +0100 Subject: [PATCH] =?UTF-8?q?=F0=9F=94=A5=20Drop=20`--strict`=20from=20the?= =?UTF-8?q?=20pytest=20config?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The `--strict` option has been deprecated in v6.2.0 and will probably resurface at some point in the future but at the moment it's recommended to use `--strict-markers` instead, which is already present. So this change just comments out `--strict` for pytest runs not to fail in the CI or dev envs. Ref: * https://github.com/pytest-dev/pytest/issues/7530 * https://github.com/pytest-dev/pytest/pull/7985 --- pytest.ini | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pytest.ini b/pytest.ini index d8d6815bf..d75ac466f 100644 --- a/pytest.ini +++ b/pytest.ini @@ -11,7 +11,10 @@ addopts = --junitxml=.test-results/pytest/results.xml # Fail on non-existing markers: - --strict + # * Deprecated since v6.2.0 but may be reintroduced later covering a + # broader scope: + # --strict + # * Exists since v4.5.0 (advised to be used instead of `--strict`): --strict-markers # `pytest-cov`: