[RowTest] as Much as Possible

Mark wrote a post about unit tests structure, and the need for similar tests to look the same.

Good points there. I like my tests to show their essence in a very visible way – the concrete values for the scenario and the assertion are more often than not just the primitives which vary between test case to another.

If you read the subject of this post you already know where I’m going with this: I really like row tests’ ability to concisely describe the variance between cases. So much so that I’d advocate using [RowTest] even if you have a couple of test cases (like in Mark’s example), to make the tests more readable.

As a side note – QuickUnit doesn’t support generating your tests in such a data driven manner yet, but we’ll get to it shortly.