pytest-django
pytest-django copied to clipboard
A Django plugin for pytest.
Hey there, I needed this personally to allow for usage of Hypothesis tests alongside pytest-django. Wanted to contribute in case you found it useful
I've been trying to get Django's test runner to run `manage.py check` at the start of the test suite in django/django#6294. It actually used to do it in 1.7 and...
https://github.com/django/django/pull/8200 was not accepted, but I think it's good to not fail with `{{ foo | default:"bar" }}` with `foo` being undefined. @codingjoe What do you think?
Continuing #759
https://docs.djangoproject.com/en/3.2/topics/testing/advanced/#django.test.TransactionTestCase.available_apps See also: PR #575 Note: Django marks this as private API so we would probably also mark it as such if we choose to add it.
When a test fails, it'd be very interesting to be able to explore the remaining test database, to better understand what happened. Of course it would be only in a...
This is what I get when running `pytest --fixtures`: ``` . . . django_db_modify_db_settings_xdist_suffix ...python3.5/site-packages/pytest_django/fixtures.py:23: no docstring available . . . django_db_modify_db_settings ...python3.5/site-packages/pytest_django/fixtures.py:51: no docstring available django_db_use_migrations ...python3.5/site-packages/pytest_django/fixtures.py:56: no docstring...
If I run one test via PyCharm I see the migrations output twice: ``` /home/guettli/projects/lala-env/bin/python /snap/pycharm-professional/230/plugins/python/helpers/pycharm/_jb_pytest_runner.py --target test_models.py::test_address_is_complete Testing started at 11:42 ... Launching pytest with arguments test_models.py::test_address_is_complete in /home/guettli/projects/lala-env/src/lala/lala/tests...
Hello, I'm dealing with a confusing issue. I have`--fail-on-template-vars` in my pytest.ini. When I run all the tests, all tests pass. But I know there are some test that should...
After upgrading our Django project from Django 1.11.8 to 2.2.6, along with pytest (from 2.9.2 to 5.2.0) and pytest-django (3.1.2 to 3.5.1), we started getting the following error in some...