Some tips and techniques for using NUnit, the testing framework used in this book.
As you read this book, you’ll see that we do a lot of testing. We write most of our tests before we write the code, one test at a time. A little test, a little code to make it work, and so on. We work that way for some good reasons, which you’ll see as we go along:
Most important, well-tested code works better. Customers like it better.
Testing as we write means we spend less time debugging. We get our programs done faster.
Testing as we write means that we don’t have those long testing cycles at the end of our projects. We like working without that death march thing.
Our tests are the first users of our code. We ...