OpenAtlas

I tested pytest, it works fine.
Currently installed:

apt install python3-pytest python3-cov 

Created two files:
pytest-cov

[report]
precision = 2
omit =
    ../openatlas/api/import_scripts/*
    ../openatlas/views/vocabs.py
skip_covered = True
sort = Cover

pytest.ini

[pytest]
addopts = --cov=openatlas --cov=tests --cov-report=html --cov-report=term --cov-report=term-missing

And then run in from IDE or shell

cd ../openatlas/tests
pytest

Location of the coverage file: /openatlas/tests/htmlcov/index.html

After some testing I discovered some things which we can discuss:

• The coverage isn't shown in the PyCharm output because of a known bug
  To fix it you can adapt the _jb_runner_tools.py file (in my case at /opt/pycharm-community/plugins/python-ce/helpers/pycharm/_jb_runner_tools.py) and move full_name = properties["name"] into the try catch block below.
• I would prefer .pytest.ini over pytest.ini as the name of the config file. Both naming work but I like the config file being at the top.
• I like using addopts = -ra -q --no-header in the ini file but but I'm not sure what the current addopts = -r w -W default does and what the motivation was.
  Most seem to be ignored by PyCharm anyway but are effecting command line usage when just executing pytest.
• pytest-flask looked interesting but I couldn't find any advantages. Running tests in parallel would have been nice but would require a definite rewrite/restructure of our test (e.g. errors because of parallel database creations)

• I would prefer .pytest.ini over pytest.ini as the name of the config file. Both naming work but I like the config file being at the top.

As you like, but on the top sounds good.

• I like using addopts = -ra -q --no-header in the ini file but but I'm not sure what the current addopts = -r w -W default does and what the motivation was.
  Most seem to be ignored by PyCharm anyway but are effecting command line usage when just executing pytest.

-r w Show a summary of warnings
-W default Show warnings that are normally hidden like Deprecation Warnings

I have used them, because I got the information that there are like 30 warnings, but not what warnings. But I didn't had much time to test everything through.

• pytest-flask looked interesting but I couldn't find any advantages. Running tests in parallel would have been nice but would require a definite rewrite/restructure of our test (e.g. errors because of parallel database creations)

We can write a new ticket for this.