Testing the Chain of Responsibility, Part 2

08/08/12 • -1 min

Download the podcast Chain Composition Behaviors We always design services for multiple clients. Even if a service (like the Processor service in our example) has only a single client today, we want to allow for multiple clients in the future. In fact, we want to promote this; any effort expended to create a service will return increasing value when multiple clients end up using

Previous Episode

Testing the Chain of Responsibility, Part 1 (redux)

Download the podcast Testing the Chain of Responsibility The Chain of Responsibility pattern (hereafter CoR) is one of the original “Gang of Four” patterns. We’re assuming you know this pattern already, but if not you might want to read about it first at the Net Objectives Pattern Repository. The basic idea is this: you have a series of rules (or algorithms) that are conceptually

Next Episode

Testing Through API's

Download the Podcast We recently got a question from Tomas Vykruta, a colleague of ours, and we felt it turned out to be such a good, fruitful question that we wanted to pass it, and our answers, along in this blog. Here is Tomas' question: Do you prefer to have unit tests written against the public API, or to test individual functions inside the API? I've seen both approaches at my company,