{"id":1701,"date":"2019-11-25T15:48:46","date_gmt":"2019-11-25T13:48:46","guid":{"rendered":"https:\/\/djangostars.com\/blog\/?p=1701"},"modified":"2025-09-12T16:02:49","modified_gmt":"2025-09-12T16:02:49","slug":"django-pytest-testing","status":"publish","type":"post","link":"https:\/\/djangostars.com\/blog\/django-pytest-testing\/","title":{"rendered":"Testing Your Django App With Pytest"},"content":{"rendered":"
\n

Helps you write better programs.
\n\u2014\u00a0pytest<\/a><\/p>\n<\/blockquote>\n

Many developers from Python community heard of and used unit testing to test their projects and knew about boilerplate code with Python and Django unittest module. But Pytest and Django suggest much more pythonic tests without boilerplate.<\/p>\n

In this comprehensive tutorial, we are talking about PyTest in Python. We have sufficient experience in this topic (what is our portfolio<\/a> worth), so if you need help or additional advice, please contact us<\/a>.<\/p>\n

Why You Should Use Pytest?<\/h2>\n

While you can get by without it when testing in Python and Django, Pytest provides a new approach for writing tests, namely, functional testing for applications and libraries. Below I\u2019ll list some pros and cons about this framework. We often use this in Django development.<\/p>\n

Pros of Using Pytest:<\/h3>\n

– Assert statements<\/a> (no need to remember `self.assert*` names)
\n– Detailed info on failures
\n– Fixtures<\/a> (explicit, modular, scalable)
\n– Additional features of fixtures (auto-use, scope, request object, nested, finalizers, etc.)
\n– Auto-discovery<\/a> of test modules and functions
\n– Marks<\/a>
\n– Parametrizing<\/a>
\n– Less boilerplate code: just create file, write function with assert and run (simple is better than complex)
\n– No Camel \u0441ase as PyUnit
\n– Plugins with over 736+external plugins and thriving community
\n– Can run unittest<\/a> and nose<\/a> test suites out of the box
\n– Python 3.5+ and PyPy 3<\/p>\n

Cons of Using Pytest:<\/h3>\n

– Requires a bit more advanced Python knowledge than using unittest<\/a>, like decorators<\/a> and simple generators<\/a>
\n– The need for a separate installation of the module. But it can be an advantage as well, because you don\u2019t depend on Python version. If you want new features, you just need to update pytest package.<\/p>\n

Short Introduction to Pytest<\/h2>\n

First of all, I would like to make a small intro to pytest philosophy and base syntax. I will do it in the format of the most frequently asked questions and answers. This is a very short intro for pytest with basic functionality, but make sure to check it as we will use it in the next parts.<\/p>\n

Q1: What are Pytest Fixtures?<\/strong><\/p>\n

Fixtures are functions that run before and after each test, like setUp and tearDown in unitest and labelled pytest killer feature. Fixtures are used for data configuration, connection\/disconnection of databases, calling extra actions, etc.<\/p>\n

All fixtures have scope argument with available values:<\/p>\n

    \n
  • function<\/strong> run once per test<\/li>\n
  • class<\/strong> run once per class of tests<\/li>\n
  • module<\/strong> run once per module<\/li>\n
  • session<\/strong> run once per session<\/li>\n<\/ul>\n

    Note:<\/strong> Default value of scope is function<\/em>.<\/p>\n

    Example of simple fixture creation:
    \n