+ 

+ Introducing new code means adding unit tests.

+ Fedora Happiness Packets uses the `Django test suite <https://docs.djangoproject.com/en/dev/topics/testing/>`__ and `pytest <https://pytest.org/>`__ for testing.

+ As a rule of thumb, consider this wisdom when writing tests:

+ 

+ * Use test functions and plain-old ``assert`` statements.

+ * Ideally, test functions should be *around* five lines and assert one thing.

+ * If you need multiple test classes, inheritance, or OOP, you might be doing it wrong.

+ * If you need to make imports from other test directories, you might be doing it wrong.

+ * If you need more than two levels of indentation, you might be doing it wrong.

+ * "There's a plugin for that!"

+   Pytest has a rich `plugin community <https://docs.pytest.org/en/latest/plugins.html>`__ with almost anything you can think of.

+   Take advantage of them!

+ * Don't use ``@mock.patch`` or ``with mock.patch``.

+   Use `pytest fixtures <https://pythontesting.net/framework/pytest/pytest-fixtures-nuts-bolts/>`__. [#]_

+ 

+ .. [#] You can still use ``mock.patch``.

+        It has more features than pytest's monkeypatch fixture.

+        But don't use it with a decorator, which has a problem of applying at import time nor using it in ``with`` statements.

+        Instead, you would use it with ``pytest-mock``, which exports the Mock API via a ``mocker`` fixture.

+        The fixture ensures the enter/exit context happens at the usual time in pytest setup/teardown.

+