[tool:pytest]
addopts = --doctest-modules --ignore setup.py --basetemp=.pytest
testpaths = tests

# Settings for running test coverage, used by pytest coverage plugin
# (in the `pytest-cov` package)
[coverage:run]
# Measure branch coverage in addition to statement coverage.
branch = True
# Measure coverage in the staticjinja directory/package
source = staticjinja

# When `coverage html` is run, where the report html is placed.
[coverage:html]
directory = .htmlcov

[flake8]
# Make flake8 play nicely with Black
max-line-length = 88

[tool:pytest]
addopts = -vv --doctest-modules --ignore setup.py --basetemp=.pytest
testpaths = tests

# Settings for running test coverage, used by pytest coverage plugin
# (in the `pytest-cov` package)
[coverage:run]
# Measure branch coverage in addition to statement coverage.
branch = True
# Measure coverage in the staticjinja directory/package
source = staticjinja

# When `coverage html` is run, where the report html is placed.
[coverage:html]
directory = .htmlcov

[flake8]
# Make flake8 play nicely with Black
max-line-length = 88

Add verbose flag to pytest
Add verbose flag to pytest

When running in CI sometimes an assert statement would fail when
comparing strings, and you don't get the whole
diff by default, so you can't actually see what's going on,
which is annoying.
See https://github.com/staticjinja/staticjinja/pull/153/checks?check_run_id=2824261687
Therefore just always run with the `-vv` flag, it's OK if it's a bit
more verbose, it's not that bad.
