-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathpytest.ini
More file actions
42 lines (39 loc) · 1.5 KB
/
Copy pathpytest.ini
File metadata and controls
42 lines (39 loc) · 1.5 KB
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
39
40
41
42
[pytest]
testpaths = tests
python_files = test_*.py
python_classes = Test*
python_functions = test_*
# --strict-markers: an unregistered @pytest.mark.foo becomes an ERROR, not a
# silent no-op. This is the single cheapest guard against "my smoke suite is
# empty because I typed @pytest.mark.smoek".
addopts =
-ra
--strict-markers
--strict-config
--tracing=retain-on-failure
--video=retain-on-failure
--screenshot=only-on-failure
--output=reports/test-results
--html=reports/report.html
--self-contained-html
markers =
smoke: fast critical-path checks. Run on every pull request.
regression: the full suite. Run nightly.
api: pure API test, no browser needed (fast).
ui: browser-driven test.
external: hits the public internet. Allowed to fail in CI (continue-on-error).
visual: screenshot comparison, needs committed baselines.
slow: takes more than ~5s; deselect with -m "not slow".
# Warnings are errors -- but only the ones you can act on.
#
# A bare `error` looks rigorous and is a trap: ResourceWarning fires when the
# GC collects our subprocess/socket handles, and a dependency bump can inject a
# DeprecationWarning from code you do not own. Both would fail a suite that has
# nothing wrong with it, and the team's fix is always to delete the setting
# entirely. Ignore third-party noise, keep everything else fatal.
filterwarnings =
error
ignore::DeprecationWarning
ignore::PendingDeprecationWarning
ignore::ResourceWarning
ignore::UserWarning