1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
|
pytest-djangoapp
================
https://github.com/idlesign/pytest-djangoapp
|release| |lic| |coverage|
.. |release| image:: https://img.shields.io/pypi/v/pytest-djangoapp.svg
:target: https://pypi.python.org/pypi/pytest-djangoapp
.. |lic| image:: https://img.shields.io/pypi/l/pytest-djangoapp.svg
:target: https://pypi.python.org/pypi/pytest-djangoapp
.. |coverage| image:: https://img.shields.io/coveralls/idlesign/pytest-djangoapp/master.svg
:target: https://coveralls.io/r/idlesign/pytest-djangoapp
Description
-----------
*Nice pytest plugin to help you with Django pluggable application testing.*
This exposes some useful tools for Django applications developers to facilitate tests authoring, including:
* Settings overriding
* Template tags testing
* User creation
* Request object creation
* Management command calls
* Mailing
* Migrations
* Messages
* DB queries audit
* Live server & client UI testing
* etc.
Suitable for testing apps for Django 1.8+.
How to use
----------
Let's say you have classical tests placing (inside application directory):
.. code-block::
package_dir
|__ myapp
| |__ __init__.py
| |__ tests
| | |__ __init__.py
| | |__ conftest.py <- Configure djangoapp here.
|
|__ setup.py
Add the following lines into `conftest.py` to configure `djangoapp` and start using it:
.. code-block:: python
# conftest.py
from pytest_djangoapp import configure_djangoapp_plugin
pytest_plugins = configure_djangoapp_plugin()
Fixtures usage examples can be found in the documentation and the source code.
Testing an entire project
-------------------------
Despite the fact that `djangoapp` is primarily aimed to reusable
Django applications testing one can use it also to test a project (a set of apps).
For that, pass a dotted settings module path into `settings` argument:
.. code-block:: python
pytest_plugins = configure_djangoapp_plugin(
settings='myproject.settings.settings_testing',
migrate=False, # If you do not want to apply migrations.
)
What about pytest-django
------------------------
`pytest-djangoapp` does not depend on `pytest-django`.
There are design decisions in `pytest-django` that might make it uncomfortable to work with.
1. It uses `setuptools` entrypoints feature for `pytest` plugin discovery. It's not a problem by itself,
but all kinds of bootstrapping with side effects made by `pytest-django` just on startup,
make the plugin a poor choice for cases of system-wide (i.e. not venv) installations.
2. Philosophy that next to no unit test should require DB access may be quite annoying.
3. Some fixtures (e.g. `django_assert_num_queries`) usability arouse questions.
Despite that `pytest-django` is nice, of course.
`pytest-djangoapp` fixtures allow the use of Django without marking all relevant tests as needing
a database, as is required by pytest-django which provides the ``django_db`` mark and db fixtures.
If you have `pytest-django` already installed, it can be disabled for projects
using `pytest-djangoapp` by adding the following lines into ``pytest.ini``:
.. code-block:: ini
# pytest.ini
[pytest]
addopts = -p no:django
Documentation
-------------
http://pytest-djangoapp.readthedocs.org/
|
