mirror of
https://github.com/ae-utbm/sith.git
synced 2025-07-11 04:19:25 +00:00
Use pytest for tests (#681)
* use pytest for tests Eh ouais, il y a que la config qui change. Pytest est implémentable par étapes. Et ça c'est beau. * rework tests with pytest * remove unittest custom TestRunner * Edit doc and CI
This commit is contained in:
@ -55,10 +55,9 @@ ipython = "^7.28.0"
|
||||
ruff = "^0.4.10"
|
||||
|
||||
[tool.poetry.group.tests.dependencies]
|
||||
coverage = "^7.5.4"
|
||||
|
||||
[tool.poetry.group.tests]
|
||||
optional = true
|
||||
pytest = "^8.2.2"
|
||||
pytest-cov = "^5.0.0"
|
||||
pytest-django = "^4.8.0"
|
||||
|
||||
[tool.poetry.group.docs.dependencies]
|
||||
sphinx-rtd-theme = "^1.0.0"
|
||||
@ -73,6 +72,10 @@ version = "1.4.25"
|
||||
[tool.ruff.lint]
|
||||
select = ["I", "F401"]
|
||||
|
||||
[tool.pytest.ini_options]
|
||||
DJANGO_SETTINGS_MODULE = "sith.settings"
|
||||
python_files = ["tests.py", "test_*.py", "*_tests.py"]
|
||||
|
||||
[build-system]
|
||||
requires = ["poetry-core>=1.0.0"]
|
||||
build-backend = "poetry.core.masonry.api"
|
||||
|
Reference in New Issue
Block a user