pytest.ini

[pytest]
# loadscope schedules a whole test class as one unit, so all of its tests land
# on the same worker. The default 'load' hands them out individually, and every
# worker that receives one sets the class-scoped fixtures up again - its own dbt
# project directory, its own schema, and, where a class fixture invokes dbt, its
# own `dbt run`. Grouping by class is what makes a class's setup run once.
#
# Measured on the functional suite at `-n auto` (12 workers, 406 tests, 230
# classes), counting setups of dbt's class-scoped `project` fixture:
#
#   --dist load       252 / 255 setups   339s / 351s
#   --dist loadgroup  290 / 287 setups   361s / 363s
#   --dist worksteal  233 / 233 setups   345s / 359s
#   --dist loadscope  230 / 230 setups   314s / 308s
#
# loadscope is the only one that reaches one setup per class, and it is also the
# fastest: the redundant setups cost more than the coarser balancing saves.
# loadgroup is worse than plain 'load' for anything unmarked - it makes every
# unmarked test its own work unit and hands them out one at a time, which
# discards the consecutive-batch locality 'load' deliberately preserves.
addopts = --dist loadscope
filterwarnings =
    ignore:.*'soft_unicode' has been renamed to 'soft_str'*:DeprecationWarning
    ignore:unclosed file .*:ResourceWarning
env_files =
    test.env
testpaths =
    tests/unit
    tests/functional
markers =
    skip_profile
    only_with_profile
    temporary: remove once the version or deployment in the reason ships