Question

I used TDD as a development style on some projects in the past two years, but I always get stuck on the same point: how can I test the integration of the various parts of my program?

What I am currently doing is writing a testcase per class (this is my rule of thumb: a “unit” is a class, and each class has one or more testcases). I try to resolve dependencies by using mocks and stubs and this works really well as each class can be tested independently. After some coding, all important classes are tested. I then “wire” them together using an IoC container. And here I am stuck: How to test if the wiring was successfull and the objects interact the way I want?

An example: Think of a web application. There is a controller class which takes an array of ids, uses a repository to fetch the records based on these ids and then iterates over the records and writes them as a string to an outfile.

To make it simple, there would be three classes: Controller, Repository, OutfileWriter. Each of them is tested in isolation.

What I would do in order to test the “real” application: making the http request (either manually or automated) with some ids from the database and then look in the filesystem if the file was written. Of course this process could be automated, but still: doesn´t that duplicate the test-logic? Is this what is called an “integration test”? In a book i recently read about Unit Testing it seemed to me that integration testing was more of an anti-pattern?

Answer 1

What you describe is indeed integration testing (more or less). And no, it is not an antipattern, but a necessary part of the sw development lifecycle.

Any reasonably complicated program is more than the sum of its parts. So however well you unit test it, you still have not much clue about whether the whole system is going to work as expected.

There are several aspects of why it is so:

• unit tests are performed in an isolated environment, so they can’t say anything about how the parts of the program are working together in real life
• the “unit tester hat” easily limits one’s view, so there are whole classes of factors which the developers simply don’t recognize as something that needs to be tested*
• even if they do, there are things which can’t be reasonably tested in unit tests – e.g. how do you test whether your app server survives under high load, or if the DB connection goes down in the middle of a request?

* One example I just read from Luke Hohmann’s book Beyond Software Architecture: in an app which applied strong antipiracy defense by creating and maintaining a “snapshot” of the IDs of HW components in the actual machine, the developers had the code very well covered with unit tests. Then QA managed to crash the app in 10 minutes by trying it out on a machine without a network card. As it turned out, since the developers were working on Macs, they took it for granted that the machine has a network card whose MAC address can be incorporated into the snapshot…