Codementor: Tutorial: How to Create Custom Exceptions in Python

Ankur Ankan is the lead developer of pgmpy, a Python library for Probabilistic Graphical Models. He mentors students at Google Summer Code and has great passion for Python programming.

This tutorial was originally posted in his blog.

While writing tests we often need to compare objects defined by us and we then have to compare each attribute of the object one by one.

Let’s take an example of a simple Car class. The Car object has two attributes speed and color.

classCar:
    def__init__(self, speed, color):
        self.speed = speed
        self.color = color

So if you try writing test for it using unittest.TestCase.AssertEqual method.

import unittestclassTestCar(unittest.TestCase):
    deftest_car_equal(self):
       car1 = Car(40, 'red')
       car2 = Car(40, 'red')
       self.assertEqual(car1, car2)

If you now try to run this test, the test case will fail.

self.assertEqual(Car(40, 'red'), Car(40, 'red'))
AssertionError: <assert.Car object at0x7f8edbc078d0> != <assert.Car object at 0x7f8edbc07908>

This is because unittest doesn’t know how to compare two Car objects.

So, we have a two options to make this work:
1. We can define a __eq__ method in Car class.
2. We can create a custom assertion class.

1. __eq__ method

__eq__ is one of the rich comparison methods. Whenever == is used on any object its __eq__ method is called. For example car1 == car2 internally calls car1.__eq__(car2).

Our new car class:

classCar:
   def__init__(self, speed, color):
      self.speed = speed
      self.color = colordef__eq__(self, another_car):
       iftype(self)==type(another_car) and self.speed==another_car.speedand
               self.color==another_car.color:
           return True
        else:
           return False

And now the same test passes. But when car1 is not equal to car2, the test fails and the output is not at all informative about why the test failed. It simply prints:

self.assertEqual(car1, car2)
AssertionError: <Carobject at0x7f1f86af6a20> != <Carobject at0x7f1f86af6a58>

So, one drawback of this approach is that we can’t show some message about why the equality failed. Showing an error message by printing it wouldn’t be a good design because when the user does a simple car1 == car2 and if they are not equal, __eq__ would still print the details of why they are not equal.

Now, we see the second approach in which we can give a detailed message about why the equality failed.

2. Custom assertion class

We can write a custom assertion class for out car class.

classAssertCarEqual:
    def assert_car_equal(self, car1, car2):
        iftype(car1) != type(car2):
            raiseAssertionError("car1 is of type: ", type(car1), " and car2 is of type: ", type(car2))
        elif car1.speed != car2.speed:
            raiseAssertionError("speed of car1: ", car1.speed, " and speed of car2: ", car2.speed)
        elif car1.color != car2.color:
            raiseAssertionError("color of car1: ", car1.color, " and color of car2: ", car2.color)

And modifying the test like this:

class TestCar(unittest.TestCase, AssertCarEqual):
    deftest_car_equal(self):
        car1 = car.Car(40, 'blue')
        car2 = car.Car(40, 'red')
        self.assert_car_equal(car1,car2)

Now when we run the test, the test fails and gives a message about why the test failed.

raiseAssertionError("color of car1: ", car1.color, " and color of car2: ", car2.color)
AssertionError: ('color of car1: ', 'blue', ' and color of car2: ', 'red')

Need Ankur’s help? Book a 1-on-1 session!

View Ankur’s Profile

or join us as an expert mentor!