Actually run the tests and also run them against Django 4.1-5.0 #428
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
scripts/test.sh
was introduced back in commit 55cb670,test_func.py
hadCommit 38f2cf2 (PR #417) removed
The tests on the main branch pass, but as the logs show, pytest never runs. And the coverage shows 0%.
In my fork all tests for
test old stuff / Django@… / [email protected]
don't do anything afterResolving dependencies...
and I've cancelled the workflow after 18 minutes. Maybe support for Python 3.7 can be dropped? It reached its EOL back in 2023-06-27. Django 3.2 LTS is the last version that supports Python 3.7 and that will reach its EOL in April 2024.