In dutch there is this saying.

Een ezel stoot zich nooit tweemaal aan dezelfde steen.

A literal translation would go like this.

A donkey never bumps into the same stone twice.

or

Even a donkey does not bump himself twice against the same stone…

A less literal translation would be this.

Fool me once, shame on you. fool me twice, shame on me.

So unit testing is all about being the donkey or the fool or both ;-).

Today I will be having an interview with Roy Osherove about his upcoming book “The Art of Unit Testing“. The book concentrates on unit testing for the .Net developer. And it covers these subjects (as taken from the manning website).

* Introduction to unit testing and the basics of writing real-world unit tests with NUnit

* Best practices for writing maintainable, trustworthy, readable tests

* Mock Objects and integration testing in-depth

...

Previous posts can be found here:

• Part One - The Beginning
• Part Two - The Domain Model
• Part Three - Testing the Schema

Setting up the repositories for our objects is where this really starts to get fun for m...

Previous posts can be found here:

• Part One - The Beginning
• Part Two - The Domain Model

In part two we set up our domain model. Now, before we can test nhibernate’s ability to work with and persist objects, we need to ensure that we’ve defined our schema well enough that NHibernate can create the Schema for us (since t...

• Part One - The Beginning

In part one we discussed what has brought me to the shameful point of using an object-relational mapper. At the risk of being ostracized from the database community, I really think this is going to be helpful for my project.

The next step is to actually build up the domain model, and set up the mappings for NHibernate. I won’t be pasting all the code in here, but I will be attaching the project itself to the next po...