Diasparsoft Logo Let's write software that people understand.

Home | Contact

Training

JUnit support

Outsourcing

The work that Diasparsoft did for us was outstanding. We are now using the software on a daily basis and their work could well have a dramatic impact on the Reds' organization in the near future. —Cincinnati Reds Baseball Club.

Publications

Tips & Tricks

Diasparsoft Toolkit

What is Diaspar?

Interesting Bits RSS

Home » Archives » March 2005 » Contract Tests

[Previous entry: "Predictable Delivery: A killer metric"] [Next entry: "Eclipse vs. IDEA"]

03/02/2005: "Contract Tests"


Contract Tests explain how a class should extend a superclass or implement and interface, so that I don't have to read a bunch of prose to figure out how to do that. Typically, a contract test case class is abstract, then I extend it and implement a creation method or two to return instances of my own implementation of the given interface. That gives me a standard battery of tests I can run to drive my implementation. It might not be perfect (I'll have n failing tests to start) but I prefer it to documentation written in prose.

So if you're delivering something you want me to extend and I need to follow more than three rules, please deliver me some contract tests.