forked from xenserver/status-report
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathpytest.ini
38 lines (36 loc) · 1.46 KB
/
pytest.ini
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
[pytest]
# By default, show reports for failed tests, and show the summary: -rF
# By default, also be verbose (needed for self-tests with pytest-8) -vv
# By default, also show the local variables in the traceback: --showlocals
addopts=-rF -vv --showlocals
# imp is only used in a unit test, will be updated to python3 later:
filterwarnings=ignore:the imp module is deprecated
# Enable live logging of the python log output, starting with log level INFO by default:
log_cli=True
log_cli_level=INFO
required_plugins=
pyfakefs
pytest-mock
# By default, run the tests in the tests directory:
testpaths=tests/
#
# Make @pytest.mark.xfail(strict=True) the default:
#
# pytest.mark.xfail(strict=True) will fail if the test passes, but the default
# is to not fail if the test passes.
#
# This is a problem because it can lead to tests that are marked as XFAIL, but
# are actually passing, and we don't notice because they are marked as XFAIL.
#
# For example, if we have a test that is marked as XFAIL, but it passes, we
# will see a XPASS instead of a FAILED. This is a problem because we don't
# notice that the test is actually passing, and we don't update the test to
# now be fixed and require it to pass instead from now on.
#
# To fix this, we can set the strict parameter to True, so that if a test is
# marked as XFAIL, but passes, it will fail. This way, we will see a FAILED
# instead of a PASSED (or XPASS).
#
# Make @pytest.mark.xfail(strict=True) the default:
#
xfail_strict=True