Open
Conversation
Author
|
No idea why the coverage upload isn't passing. I noticed that in job, there is |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Following #207 , I started playing with the project and getting tests running:
https://tox.wiki/en/4.0.3/faq.html#tox-4-changed-ini-rules
test_reqs.txtto be consistent with tox.ini (versions and packages in test_reqs.txt were outdated)manage.pyfile pointing to testtests.test_settingsconfig file.First 2 were breaking my test runs.
3rd one allows running tests simply by running
python manage.py testin console - so "django way" of running tests. That means I can run every single test method by simply clicking icon in PyCharm, yay!I haven't dived deeper into
runtests.pyandpost_processor_runtests, but from first glance it seems like these could be fully removed - 1st by just doingpython manage.py testand the second by running it with--testrunner tests.post_processor.discover_tests.DiscoverPostProcessorRunner.