Question

Let’s say I am using a framework that has a class called Animal.

class Animal(object):
    def speak(self):
        logging.info(self.sound)

I have to subclass this object in order to use it and it might look something like this:

class Dog(Animal):
    def __init__(self):
        self.sound = 'Woof Woof'

The way I see it I could do two things. The first is something like like this:

dog = Dog()
assert dog.sound == 'Woof Woof'

The second option is to mock out logging.info and check if it was called. I have mixed feelings about both of them.

The first one feels like I am just testing my configuration and the second one feels like I am not actually testing the object I want.

I am using this simple example because maybe then people that don’t use Django could give me some pointers. The real problem I am having involves Django generic views.

For example I can have this template view:

class HomeView(TemplateView):
    template_name = 'home.html'

Do I just test if template_name has the correct value or do I use the test client to do a higher level test to test the complete view?

Answer 1

No, make sure the parent object is tested properly (with mocking if necessary) and test the sub-objects methods separately. This fits with the encapsulation concept (making matters local).

If you don’t, a large project with many classes will drain all your coding resources for no added value.