2018-11-14 10:10:45 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-django: updated to 3.4.4
3.4.4:
Bugfixes
* Refine the django.conf module check to see if the settings really are
configured.
* Avoid crash after OSError during Django path detection.
Features
* Add parameter info to fixture assert_num_queries to display additional message \
on failure.
Docs
* Improve doc for django_assert_num_queries/django_assert_max_num_queries.
* Add warning about sqlite specific snippet + fix typos.
Misc
* MANIFEST.in: include tests for downstream distros.
* Ensure that the LICENSE file is included in wheels.
* Run black on source.
|
2018-10-02 10:45:10 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-django: updated to 3.4.3
3.4.3:
Bugfixes
Fix OSError with arguments containing :: on Windows
|
2018-08-28 13:02:37 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-django: updated to 3.4.2
3.4.2:
Bugfixes
- Changed dependency for pathlib to pathlib2.
- Fixed code for inserting the project to sys.path with pathlib to use an \
absolute path, regression in 3.4.0
|
2018-08-18 23:14:49 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-django: updated to 3.4.1
3.4.1:
Unknown changes
3.4.0:
Features
Added new fixture django_assert_max_num_queries.
Added support for connection and returning the wrapped context manager with \
django_assert_num_queries.
Added support for resetting sequences via django_db_reset_sequences.
Bugfixes
Made sure to not call django.setup() multiple times.
Compatibility
Removed py dependency, use pathlib instead
|
2018-08-07 12:11:22 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-django: updated to 3.3.3
3.3.3:
Bug fixes
Fixed registration of ignore_template_errors() marker, which is required with \
pytest --strict
Fixed another regression with unittest
Docs
Use sphinx_rtf_theme
Minor fixes.
|
2018-06-24 13:19:33 by Adam Ciarcinski | Files touched by this commit (3) | |
Log message:
py-test-django: updated to 3.3.2
3.3.2:
Unknown changes
3.3.1:
Bug fixes
* Fixed test for classmethod with Django TestCases again
Compatibility
* Support Django 2.1 (no changes necessary)
|
2018-06-16 08:23:35 by Adam Ciarcinski | Files touched by this commit (2) | |
Log message:
py-test-django: updated to 3.3.0
3.3.0:
Features
Added new fixtures django_mail_dnsname and django_mail_patch_dns, used by \
mailoutbox to monkeypatch the DNS_NAME used in django.core.mail to improve \
performance and reproducibility.
Bug fixes
Fixed test for classmethod with Django TestCases
Fixed RemovedInPytest4Warning: MarkInfo objects are deprecated
Fixed scope of overridden settings with live_server fixture: previously they \
were visible to following tests
|
2018-04-18 09:09:03 by Adam Ciarcinski | Files touched by this commit (3) | |
Log message:
py-test-django: updated to 3.2.1
3.2.1
Fix automatic deployment to PyPI.
3.2.0
Features:
Added new fixture django_assert_num_queries for testing the number of database \
queries
–fail-on-template-vars has been improved and should now return full/absolute path
Support for setting the live server port
unittest: help with setUpClass not being a classmethod
Bug fixes:
Fix –reuse-db and –create-db not working together
Numerous fixes in the documentation. These should not go unnoticed.
Compatibilitya:
Support for Django 2.0 has been added.
Support for Django before 1.8 has been dropped.
|
2018-03-24 18:06:44 by Joerg Sonnenberger | Files touched by this commit (2) |
Log message:
Relax overly restrictive dependency.
|
2018-01-11 15:07:11 by Adam Ciarcinski | Files touched by this commit (4) |
Log message:
py-test-django: added version 3.1.2
pytest-django allows you to test your Django project/applications with the
pytest testing tool.
Running your test suite with pytest-django allows you to tap into the features
that are already present in pytest. Here are some advantages:
* Manage test dependencies with pytest fixtures.
* Less boilerplate tests: no need to import unittest, create a subclass with
methods. Write tests as regular functions.
* Database re-use: no need to re-create the test database for every test run.
* Run tests in multiple processes for increased speed (with the pytest-xdist
plugin).
* Make use of other pytest plugins.
* Works with both worlds: Existing unittest-style TestCase's still work
without any modifications.
|