OlenaYefymenko
commented
10 months ago @webknjaz I've implemented the coverage configuration as we did in my previous project. However, you mentioned an option regarding this:
#!/usr/bin/env python
"""Django's command-line utility for administrative tasks."""
import os
import sys
def main():
os.environ.setdefault("DJANGO_SETTINGS_MODULE", "myproj.settings")
# MyProject Customization: run coverage.py around tests automatically
try:
command = sys.argv[1]
except IndexError:
command = "help"
running_tests = command == "test"
if running_tests:
from coverage import Coverage
cov = Coverage()
cov.erase()
cov.start()
try:
from django.core.management import execute_from_command_line
except ImportError as exc:
raise ImportError(
"Couldn't import Django. Are you sure it's installed and "
"available on your PYTHONPATH environment variable? Did you "
"forget to activate a virtual environment?"
) from exc
execute_from_command_line(sys.argv)
if running_tests:
cov.stop()
cov = Coverage()
cov.save()
covered = cov.report()
if covered < 100:
raise SystemExit(1)
if __name__ == "__main__":
main()I have doubts about whether I should keep the configuration as it is in the current PR or add it into manage.py using contextlib.nullcontext(). However, I've read that using a coveragerc file is preferable.
webknjaz
This patch provides the coverage configuration, updates the project dependencies accordingly, and adds tests to the CI pipeline. This PR sets the stage for the next, where test functions will be integrated into the project.
Related to #18