You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unit Testing: Do no run in debug mode in order to reduce logging (#13241)
* Unit Testing: Do no run in debug mode in order to reduce logging
Viewing a failed test in the GHA logs is not very helpful without rendering the raw view because there are 50k+ lines of debug logs. Reducing the logging verbosity would make the tests quite a bit faster as well as finding failures easier in the GHA UI
* Remove verbosity from unit test commands
python3 manage.py test unittests --keepdb --no-input --exclude-tag="non-parallel" --exclude-tag="transactional"|| {
84
84
exit 1;
85
85
}
86
-
python3 manage.py test unittests -v 3 --keepdb --no-input --tag="non-parallel"|| {
86
+
python3 manage.py test unittests --keepdb --no-input --tag="non-parallel"|| {
87
87
exit 1;
88
88
}
89
89
# Running one unit tests that inherits from TransactionTestCase somehow changes the behaviour of how Django loads fixtures into the database.
90
90
# Meaning any test after this one would fail to load our dojo_testdata.json fixture. In a way this makes sense as it contains some data integrity problems.
91
91
# I tried to fix these in https://github.com/DefectDojo/django-DefectDojo/pull/13217.
92
92
# For now here we run the only TranscationTestCase at the end to avoid the problem.
93
-
python3 manage.py test unittests -v 3 --keepdb --no-input --tag="transactional"|| {
93
+
python3 manage.py test unittests --keepdb --no-input --tag="transactional"|| {
0 commit comments