Skip to content

Testing

Unit and functional tests are written to aid in application stability and to assist in preventing regression bugs. As part of development the developer working on a Merge/Pull request is to ensure that tests are written. Failing to do so will more likely than not ensure that your Merge/Pull request is not merged.

We use PyTest as the testing framework. As such, All available features of pytest are available. We have slightly deviated from the standard naming convention wherein test class must be suffixed with PyTest. Please see below for more details.

Note

As of release v1.3, the UI has moved to it's own project with the current Django UI feature locked and depreciated.

Note

These docs are currently undergoing a rewrite as how we write and expect tests to be written has changed.

Directory Structure

Each module is to contain a tests directory of the model being tested with a single file for grouping of what is being tested. for items that depend upon a parent model, the test file is to be within the child-models test directory named with format test_<type>_<model name>_<component name>. Format for the test filename is as follows:

  • Type - The test type, which is one of unit, functional, ui etc.

  • model_name - the value of the models verbose_name with the space char \s replaced with underscore _.

  • component name - The component being tested, which is one of ViewSet, Serializer, API etc.

example file system structure showing the layout of the tests directory for a module.

.
├── tests
│   ├── functional
│   │   ├── __init__.py
│   │   └── <model name>
│   │       └── test_<type>_<model name>_<component name>.py
│   ├── __init__.py
│   ├── integration
│   │   ├── __init__.py
│   │   └── <model name>
│   │       └── test_<type>_<model name>_<component name>.py
│   ├── ui
│   │   ├── __init__.py
│   │   └── <model name>
│   │       └── test_<type>_<model name>_<component name>.py
│   └── unit
│       ├── __init__.py
│       └── <model name>
│           ├── test_<type>_<model name>.py
│           ├── test_<type>_<model name>__api.py
│           ├── test_<type>_<model name>_history.py
│           ├── test_<type>_<model name>_history_permission.py
│           ├── test_<type>_<model name>_notes.py
│           ├── test_<type>_<model name>_permission_api.py
│           ├── test_<type>_<model name>_serializer.py
│           └── test_<type>_<model name>_viewsets.py

Tests are broken up into the type the test is (sub-directory to test), and they are unit, functional, UI and integration. These sub-directories each contain a sub-directory for each model they are testing.

Writing Tests

We use class based tests with each test case being its own function. Naming of test classes is in CamelCase in format <class name><suffix>. class name is the name of the actual class being tested with the suffix being one of the following:

  • TestCases - Contains the test cases for the class being tested.

    This class contains all of the tests for the area being tested.

  • InheritedCases - Is to inherit from TestCases and contains any additional tests for classes that inherit from the class being tested

    This class is used by sub-models and/or sub-classes that inherit from the area being tested

  • PyTest - Not to inherit from TestCases. This special suffix tells pytest during test collection, to build the test suite using PyTest.

    This class is the class that test the actual object(s) being tested.

Do not deviate from the test class name suffix as we have setup pytest to automagically create the test classes based off of these names. For instance, classes that are suffixed (not prefixed as is the pytest norm), will be added as a test class and not as an abstract class.

Test Cases are to test one object and one object only. If the object to be tested contains multiple objects/moving parts, instantiate that object within a fixture. Some test may require that the test be setup before the tests begin. This is done via fixture called class_setup that is called with scope='class', autouse = True. Each test case must be documented using docstring.

Tip

If you inherit from an InheritedCases Class and there is a class_setup fixture, don't forget to import this into your test suite. This ensures it's available for use when running tests

Fixtures

Fixtures are used to setup the test and to pass objects to test should they require it. We have some common and globally available fixtures, they are:

  • create_model Creates the model from class var kwargs_create_item: dict

  • organization_one Organization called org one

  • organization_two Organization called org two

  • recursearray Search through an array using dot notation (dict.list.dict i.e. dict_1.2.dict_3). The array can be a dict, list or combination of both.

Info

Unless otherwise mentioned, fixtures are scope = 'class'

There may also be a requirement that you add additional fixtures, they are:

  • model This fixture should be defined in conftest.py in the test suite files directory. Only required if the model is required to be worked with.

    ``` py filename="conftest.py"

    import pytest

    from itim.models.request_ticket import RequestTicket

    @pytest.fixture( scope = 'class') def model(request):

    request.cls.model = RequestTicket

yield request.cls.model

del request.cls.model    # Don't forget to clean-up any objects created.

    ```

Due to how pytest and pytest-django works, there is no method available for class based tests that allows both database access and inheritance. As such, all test classes are expected to have a fixture called class_setup that is scope = 'class' and autouse = True that is intended to serve as the method of setting up the test suite. This fixture should also include as dependencies any other fixture required for setup and in the order required for setup to finish without error. This fixture (class_setup) is also intended to be an over-writable fixture in parent classes should you need to customise the load order of fixtures.

Tip

Fixtures that are scope = 'class' are unable to accept fixture db including other database related marks, which is problematic for a class fixture that requires database access. As a workaround the following works: 

@pytest.fixture( scope = 'class')
def setup_post(self, django_db_blocker):

    with django_db_blocker.unblock():

        # db transactions

    yield item    # required so that cleanup can be done
                  # Note: use return if the db transaction was to create
                  # a single object.

    with django_db_blocker.unblock():

        # db transactions for cleanup

Running Tests

Test can be run by running the following:

  1. pip install -r requirements_test.txt -r requirements.txt

  2. make prepare

  3. make test-unit for running Unit tests or make test-functional for running Functional tests.

If your developing using VSCode/VSCodium the testing is available as is the ability to attach a debugger to the test.

Test Case docs to be re-written

Note

The documentation below this section are being re-factored to meet an updated method of testing (documentation above this section). Until all test suites/cases have been re-written, the docs within and below this section may still be applicable.

~~Unit and functional tests are written to aid in application stability and to assist in preventing regression bugs. As part of development the developer working on a Merge/Pull request is to ensure that tests are written. Failing to do so will more likely than not ensure that your Merge/Pull request is not merged.~~

User Interface (UI) test are written if applicable to test the user interface to ensure that it functions as it should. Changes to the UI will need to be tested.

~~!!! note~~ ~~As of release v1.3, the UI has moved to it's own project with the current Django UI feature locked and depreciated.~~

Integration tests will be required if the development introduces code that interacts with an independent third-party application.

Available Test classes

To aid in development we have written test classes that you can inherit from for your test classes

  • API Permission Checks

    These test cases ensure that only a user with the correct permissions can perform an action against a Model within Centurion

    • api.tests.abstract.api_permissions_viewset.APIPermissionAdd Add permission checks

    • api.tests.abstract.api_permissions_viewset.APIPermissionChange Change permission check

    • api.tests.abstract.api_permissions_viewset.APIPermissionDelete Delete permission check

    • api.tests.abstract.api_permissions_viewset.APIPermissionView View permission check

    • api.tests.abstract.api_permissions_viewset.APIPermissions Add, Change, Delete and View permission checks

  • API Field Checks

    These test cases ensure that all of the specified fields are rendered as part of an API response

    • api.tests.abstract.api_fields.APICommonFields Fields that should be part of ALL API responses

    • api.tests.abstract.api_fields.APIModelFields Fields that should be part of ALL model API Responses. Includes APICommonFields test cases

    • api.tests.abstract.api_fields.APITenancyObject Fields that should be part of ALL Tenancy Object model API Responses. Includes APICommonFields and APIModelFields test cases

Writing Tests - Old

~~We use class based tests. Each class will require a setUpTestData method for test setup. To furhter assist in the writing of tests, we have written the test cases for common items as an abstract class. You are advised to inherit from our test classes (see above) as a starting point and extend from there.~~

~~Naming of test classes is in CamelCase in format <Model Name><what's being tested> for example the class name for device model history entry tests would be DeviceHistory.~~

~~Test setup is written in a method called setUpTestData and is to contain the setup for all tests within the test class.~~

~~Test cases themselves are written within the test class within an appropriately and uniquely named method. Each test case is to test one and only one item.~~

Example of a model history test class.

import pytest
import requests

from django.test import TestCase, Client

from core.models.history import History
from core.tests.abstract.history_entry import HistoryEntry
from core.tests.abstract.history_entry_parent_model import HistoryEntryParentItem



class DeviceHistory(TestCase, HistoryEntry, HistoryEntryParentItem):


    model = Device


    @classmethod
    def setUpTestData(self):
        """ Setup Test """

~~Each module is to contain a tests directory of the model being tested with a single file for grouping of what is being tested. for items that depend upon a parent model, the test file is to be within the child-models test directory named with format test_<model>_<parent app>_<parent model name>~~

~~example file system structure showing the layout of the tests directory for a module.~~

.
├── tests
│   ├── functional
│   │   ├── __init__.py
│   │   └── <model name>
│   │       └── test_<model name>_a_tast_name.py
│   ├── __init__.py
│   ├── integration
│   │   ├── __init__.py
│   │   └── <model name>
│   │       └── test_<model name>_a_tast_name.py
│   ├── ui
│   │   ├── __init__.py
│   │   └── <model name>
│   │       └── test_<model name>_a_tast_name.py
│   └── unit
│       ├── __init__.py
│       └── <model name>
│           ├── test_<model name>.py
│           ├── test_<model name>_api.py
│           ├── test_<model name>_core_history.py
│           ├── test_<model name>_history_permission.py
│           ├── test_<model name>_permission_api.py
│           ├── test_<model name>_permission.py
│           ├── test_<model name>_serializer.py
│           └── test_<model name>_viewsets.py

~~Tests are broken up into the type the test is (sub-directory to test), and they are unit, functional, UI and integration. These sub-directories each contain a sub-directory for each model they are testing.~~

Items to test include, and are not limited to:

  • CRUD permissions admin site

  • CRUD permissions api site

  • can only access organization object

  • can access global object (still to require model CRUD permission)

  • history

    • saves history with parent pk and parent class

      add to model class the following

      @property
def parent_object(self):
    """ Fetch the parent object """

    return self.<item that is the parent>

      history should now be auto saved as long as class core.mixin.history_save.SaveHistory is inherited by model.

    • history is deleted when item deleted if parent_pk=None or if has parent_pk deletes history on parent pk being deleted.

  • model - any customizations

  • API Fields

    Field(s) exists, Type is checked

  • Serializer Validations

About:

This page forms part of our Project Centurion ERP.

Page Metadata
Version: ToDo: place files short git commit here
Date Created: 2024-06-17
Date Edited: 2025-04-24

Contribution:

Would You like to contribute to our Centurion ERP project? You can assist in the following ways:

 

ToDo: Add the page list of contributors