We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am on windows 10 The environment is miniconda as in the django-crash-course book.
After running the coverage run -m pytest
Test session starts (platform: win32, Python 3.8.2, pytest 5.3.5, pytest-sugar 0.9.2) django: settings: config.settings.test (from option) rootdir: C:\Users\Rahul\AppData\Roaming\plrplus\fastest\django-tests\everycheese, inifile: pytest.ini plugins: django-test-plus-1.4.0, django-3.9.0, sugar-0.9.2 collecting ... everycheese/users/tests/test_forms.py ✓ 11% █▎ everycheese/users/tests/test_models.py ✓ 22% ██▎ everycheese/users/tests/test_urls.py ✓ 33% ███▍ everycheese/users/tests/test_urls.py ✓✓ 44% ████▌ everycheese/users/tests/test_urls.py ✓✓✓ 56% █████▋ everycheese/users/tests/test_views.py ✓ 67% ██████▋ everycheese/users/tests/test_views.py ✓✓ 78% ███████▊ everycheese/users/tests/test_views.py ✓✓✓ 89% ████████▉ everycheese/users/tests/test_views.py ✓✓✓✓ 100% ██████████ Results (1.74s): 9 passed
after running coverage report
No data to report.
That is inconsistent with what is in the book.
I smelled something fishy. I then opened .coveragerc
[run] include = everycheese/* omit = *migrations*, *tests* plugins = django_coverage_plugin
That seems ok.
for testing, I just deleted the file.
running above codes after deleting .coveragerc file gave.
------------------------------------------------------------------------------------------- config\__init__.py 0 0 100% config\settings\__init__.py 0 0 100% config\settings\base.py 58 1 98% config\settings\test.py 8 0 100% config\urls.py 12 4 67% everycheese\__init__.py 2 0 100% everycheese\conftest.py 13 0 100% everycheese\contrib\__init__.py 0 0 100% everycheese\contrib\sites\__init__.py 0 0 100% everycheese\contrib\sites\migrations\0001_initial.py 6 0 100% everycheese\contrib\sites\migrations\0002_alter_domain_unique.py 5 0 100% everycheese\contrib\sites\migrations\0003_set_site_domain_and_name.py 11 4 64% everycheese\contrib\sites\migrations\__init__.py 0 0 100% everycheese\users\__init__.py 0 0 100% everycheese\users\admin.py 12 0 100% everycheese\users\apps.py 10 0 100% everycheese\users\forms.py 18 0 100% everycheese\users\migrations\0001_initial.py 8 0 100% everycheese\users\migrations\0002_user_bio.py 4 0 100% everycheese\users\migrations\__init__.py 0 0 100% everycheese\users\models.py 9 0 100% everycheese\users\tests\__init__.py 0 0 100% everycheese\users\tests\factories.py 14 0 100% everycheese\users\tests\test_forms.py 15 0 100% everycheese\users\tests\test_models.py 5 0 100% everycheese\users\tests\test_urls.py 13 0 100% everycheese\users\tests\test_views.py 40 0 100% everycheese\users\urls.py 4 0 100% everycheese\users\views.py 23 0 100% ------------------------------------------------------------------------------------------- TOTAL 290 9 97%
Not what exactly in the book but acceptable compared to no data to report
no data to report
Am I missing something, or this is due to buggy windows as always?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I am on windows 10
The environment is miniconda as in the django-crash-course book.
After running the coverage run -m pytest
after running coverage report
No data to report.
That is inconsistent with what is in the book.
I smelled something fishy. I then opened .coveragerc
That seems ok.
for testing, I just deleted the file.
running above codes after deleting .coveragerc file gave.
Not what exactly in the book but acceptable compared to
no data to report
Am I missing something, or this is due to buggy windows as always?
The text was updated successfully, but these errors were encountered: