Files
esp-matter/pytest.ini
T
Shubham Patil fe57fa6cf1 ci: add QEMU target to uni-test-app to be able to run in ci
- Add pytest_unit_test_app.py with per-group test functions (each gets
  a fresh QEMU boot to handle the single esp_matter::start() constraint)
- Add build_unit_test_app_qemu and pytest_unit_test_app_qemu CI jobs
- Disable WiFi and use QEMU virtual Ethernet in sdkconfig.defaults
- Register host_test and qemu pytest markers
- Document local QEMU test setup in README
2026-03-25 17:49:40 +05:30

43 lines
1.0 KiB
INI

[pytest]
python_files = pytest_*.py
# ignore PytestExperimentalApiWarning for record_xml_attribute
# set traceback to "short" to prevent the overwhelming tracebacks
addopts =
-s
--embedded-services esp,idf
--tb short
--strict-markers
--skip-check-coredump y
--logfile-extension ".txt"
# ignore DeprecationWarning
filterwarnings =
ignore::_pytest.warning_types.PytestExperimentalApiWarning
markers =
# target markers
esp32c3: support esp32c3 target
esp32c2: support esp32c2 target
esp32c6: support esp32c6 target
esp32h2: support esp32h2 target
esp32s3: support esp32s3 target
# env markers
esp_matter_dut: esp matter runner which have single dut
host_test: test runs on host machine (not on target hardware)
qemu: test runs under QEMU emulation
# log related
log_cli = True
log_cli_level = INFO
log_cli_format = %(asctime)s %(levelname)s %(message)s
log_cli_date_format = %Y-%m-%d %H:%M:%S
# junit related
junit_family = xunit1
## log all to `system-out` when case fail
junit_logging = stdout
junit_log_passing_tests = False