# Day 25 to 28 - Testing code with pytest

Published:

Topics: Testing code with pytest

Writing test functions for our code is extremely important. Since I have been lazy writing test code myself, I want to spend a little more time on this topic. My favorite testing framework is pytest. I’m not an expert on testing, so please consider this post an introduction to testing rather than a thorough guide.

## Why pytest?

Using pytest has several advantages. First of all, pytest makes testing very easy because its syntax is simple and easy to understand. Furthermore, it offers pretty and useful failure information. Also, we often need less code with pytest than required to achieve equivalent functionality with frameworks like unittest.

You can install pytest using pip install pytest.

## What makes a good test function?

I have a simple acflynnym that helps me remember how a good test function should look like. I found it in this stackoverflow post. A good test function should be A (fast) TRIP:

Automatic: Test functions should be invoked automatically and we should automatically check the results for pass/fail.

Fast: Good test functions run fast. If test code requires too much time, it will slow down production time and we won’t run it as often as is desirable.

Thorough: We should ensure that all key scenarios are tested.

Repeatable: A test function should produce the same result each and every time it’s executed.

Independent: A test should only test one thing at a time! Also, test functions should be independent of each other and no assumptions should be made about the order in which tests are executed.

Professional: Test functions should contain clean, precise and readable code.

## How testing functions should be named

Test functions should have long and descriptive names. Why? Because the test function are never called explicitely by the user. However, the function names will be displayed when a test fails. So if you want to know what functionality isn’t working it’s very useful to have a test function named, for example, test_square_of_negative_number() instead of just square().

## Basic usage of pytest

First of all, we will create a separate folder that holds our test functions. We will start with a file for testing the CastleKilmereMember class. In the next days and weeks, I will add more test code for the other classes and methods. In pytest file names should start or end with “test”, so we will name our test file test_castle_kilmere_member_class.py. Before creating test functions for our Magical Universe, let’s take a quick look at how a simple test function might look like.

Let’s take our say_words() function from day 5 as an example. The function looks as follows:

def say_words(person, words):
return f"{person} says: '{words}'"


A test function might look like this:

def test_say_words():
assert say_words("Aurora", "Careful Quintus!") == "Aurora says: Careful Quintus!"


We can run the test by running the command pytest from the command line within the test_code folder. The test should run without errors.

## Testing the CastleKilmereMember class

Let’s create a few tests that ensure that a Castle Kilmere member is created correctly and that we can add positive and negative traits, as well as check whether a member possesses a certain trait.

def test_correctness_of_attributes_():
bromley = CastleKilmereMember('Bromley Huckabee', 1959, 'male')
assert bromley.name == 'Bromley Huckabee'
assert bromley.birthyear == 1959
assert bromley.sex == 'male'

bromley = CastleKilmereMember('Bromley Huckabee', 1959, 'male')
assert bromley._traits == {'kind': True, 'tidy-minded': True}

bromley = CastleKilmereMember('Bromley Huckabee', 1959, 'male')
assert bromley._traits == {'mean': False}

def test_exhibit_traits():
bromley = CastleKilmereMember('Bromley Huckabee', 1959, 'male')

assert bromley.exhibits_trait('kind') == True
assert bromley.exhibits_trait('mean') == False
assert bromley.exhibits_trait('smart') == None


## Pytest fixtures

Since our Magical Universe contains mostly classes we have to create at least one member of the CastleKilmereMember class before we can test any of its functions. As an effect, we repeatedly used the same line of code to instantiate Bromley Huckabee. Is there a way to avoid this? Of course! There is a feature in pytest called fixtures. Fixtures can be used to encapsulate code that is repeatedly needed for (some) test functions.

We can create a fixture using the @pytest.fixture decorator and pass the fixture as an argument to the test functions that need it. So we could change our test code in the following way:

import pytest
from magical_universe.magical_universe import CastleKilmereMember

@pytest.fixture
def bromley():
bromley = CastleKilmereMember('Bromley Huckabee', 1959, 'male')
return bromley

@pytest.fixture
def bromley_with_traits():
bromley = CastleKilmereMember('Bromley Huckabee', 1959, 'male')
return bromley

def test_correctness_of_attributes_(bromley):
assert bromley.name == 'Bromley Huckabee'
assert bromley.birthyear == 1959
assert bromley.sex == 'male'

assert bromley._traits == {'kind': True, 'tidy-minded': True}

assert bromley._traits == {'mean': False}

def test_exhibit_traits(bromley_with_traits):
assert bromley_with_traits.exhibits_trait('kind') == True
assert bromley_with_traits.exhibits_trait('mean') == False
assert bromley_with_traits.exhibits_trait('smart') == None


Fixtures are much more powerful than this. So if you want to learn more about them consider reading the pytest docs on fixtures.

## Testing output printed to the shell

Our print_traits() function prints the positive and negative traits. So we need a way to test whether the printed output is correct. This can be done using the capfd fixture as explained in this stackoverflow post:

def test_print_traits(capfd, bromley_with_traits):
bromley_with_traits.print_traits()
stdout = stdout.strip()
assert stdout == 'Bromley Huckabee is kind, tidy-minded but not mean'



## Testing for exceptions

To show how we can test whether our code raises a certain exception, we can try to create a CastleKilmereMember without any attributes. This should raise a TypeError:

def test_init_raises_exception_with_missing_arguments():
with pytest.raises(TypeError):
bromley = CastleKilmereMember()


## Full test code for CastleKilmereMember class

This test code can also be found on the GitHub repo.

import pytest
from magical_universe.magical_universe import CastleKilmereMember

@pytest.fixture
def bromley():
bromley = CastleKilmereMember('Bromley Huckabee', 1959, 'male')
return bromley

@pytest.fixture
def bromley_with_traits():
bromley = CastleKilmereMember('Bromley Huckabee', 1959, 'male')
return bromley

def test_correctness_of_attributes_(bromley):
assert bromley._name == 'Bromley Huckabee'
assert bromley.birthyear == 1959
assert bromley.sex == 'male'

assert bromley._traits == {'kind': True, 'wild': True}

assert bromley._traits == {'mean': False}

def test_exhibit_traits(bromley_with_traits):
assert bromley_with_traits.exhibits_trait('kind') == True
assert bromley_with_traits.exhibits_trait('mean') == False
assert bromley_with_traits.exhibits_trait('smart') == None

def test_print_traits(capfd, bromley_with_traits):
bromley_with_traits.print_traits()
stdout = stdout.strip()
assert stdout == 'Bromley Huckabee is kind, tidy-minded but not mean'

def test_init_raises_exception_with_missing_arguments():
with pytest.raises(TypeError):
bromley = CastleKilmereMember()

def test_says(bromley):
assert bromley.says("Hi Cleon!") == "Bromley Huckabee says: Hi Cleon!"

def test_name_property(bromley):
assert bromley.name == 'Bromley Huckabee'

def test_age_property(bromley):
assert bromley.age == 59 # this holds only if the current year is 2018!

def test_repr_output(capfd, bromley):
print(bromley)