use a test runner that is declared in settings #66
Conversation
This file contains 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
|
Thanks for the PR! I have restructured the code a bit to avoid It does not really make sense to be able to configure the test runner when using pytest-django, since you are then not using Django's test runner anymore. :-) It was historically used within pytest-django since some of the test environment setup was done there. Starting with Django 1.6, that is no longer needed. If you have a real use case for having the runner configurable, please open a new issue or PR. |
|
No :). Just wanted to get rid of deprecation warnings about using an old test runner ;) |
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.
In "Django>1.6" i noticed a small warning about deprecation of
django.test.simple.DjangoTestSuiteRunner. I think this PR fixes this.