-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow setting the live server port. #500
Conversation
Codecov Report
@@ Coverage Diff @@
## master #500 +/- ##
==========================================
+ Coverage 92% 92.02% +0.01%
==========================================
Files 33 33
Lines 1627 1643 +16
Branches 140 142 +2
==========================================
+ Hits 1497 1512 +15
Misses 93 93
- Partials 37 38 +1
Continue to review full report at Codecov.
|
Thanks! Can you cover your patch with tests, please? |
My changes in fixtures.py should already be covered by test_fixtures.py. I'm not sure why they are shown as not covered, as most of the test code (except the one for versions 1.11.0 up to 1.11.2) seems to have been run. |
You are right, there seems to be an issue with the coverage reporting. Please rebase it on master and force-push - let's see if that fixes it. |
I think #537 should have fixed this. |
Coverage report seems to be correct now, but it shows that we do not test the non-current Django 1.11 (< 1.11.2 IIRC). |
This patch solves our problems with testing our django REST framework application with selenium. Our Angular frontend doesn't really know what port to connect to otherwise. So thank you ^^ |
Thank you! |
* Allow setting the live server port for Django >= 1.11.2. * Removed warning when specifying live server port with Django >= 1.11 < 1.11.2. * Added test for specifying a live server port with Django >= 1.11.2.
As the possibility to define a fixed live server port has been added back in Django 1.11.2 (https://code.djangoproject.com/ticket/28212), I'd like to have it available in pytest-django as well.