program selection system

It has been over six years since the first release of NUnit 2.0. In that time there have been literally millions of tests that have been authored. Many of these tests have become invaluable resources for their teams. Unfortunately there have been others that have not been maintained and were viewed as a waste of effort. What separates tests that are maintained from tests that are discarded?

Do you have a preferred way to write unit tests?

Could you describe it to your pairing partner? Could you describe it to your team? Could you intentionally adjust it to suit a particular testing context?

If your team does not have a shared, explicit unit testing philosophy you’re not getting full value from your testing efforts.

In this tutorial you will learn a simple, powerful technique to describe your unit test philosophy.