pytest.ini

; pytest scope for c64-https.
;
; This repo's test suites are NOT pytest suites. The C64 suites under
; tools/ are driven by tools/run_all_tests.py, which allocates a VICE
; instance per suite and calls run_tests(transport, labels, seed); their
; `test_*` functions take positional arguments, not fixtures, so pytest
; can only ever report them as "fixture 'transport' not found". The live
; rig scripts in tests/ are main() programs needing sudo and a network
; rig (see tests/README.md), and those in tools/uci/ need a real U64E or
; C64U on the LAN (see tools/uci/README.md).
;
; Only a handful of modules are pure-logic and genuinely runnable by
; pytest. testpaths names them explicitly, so that `pytest` with no
; arguments from the repo root is a fixed, honest set rather than
; whatever the tree happens to look like, and so that it never wanders
; into directories where every file named test_*.py contributes zero
; tests (tests/, tools/uci/, libs/).
;
; testpaths only applies when pytest runs from the rootdir. That is why
; the rig scripts had to be RENAMED to rig_*.py as well, in tests/ and in
; tools/uci/ alike: a rename holds from any working directory, config
; does not.
;
; Both halves are enforced, in both directions, by
; tools/test_pytest_boundary.py: add a pure-logic tools/test_*.py module
; and that guard fails until you list it in testpaths; drop tests/ or
; tools/uci/ from norecursedirs, or let a test_*.py file reappear in
; either, and it fails too.
;
; A green run here does NOT mean the C64 test suites passed. conftest.py
; prints that on every invocation; do not remove it.

[pytest]
testpaths =
    tools/test_net_test_env.py
    tools/test_package_verify.py
    tools/test_pytest_boundary.py

norecursedirs = .git libs ip65 ip65-build build dist tests tools/uci

; A collection error must never be mistaken for a passing run.
addopts = -ra