Question

More than a question, per se, this is an attempt to compare notes
with other people. I wrote a generic History class that emulates
the functionality of a browser’s history. I am trying to wrap my
head around how far to go when writing unit tests for it. I am
using NUnit. Please share your testing approaches below.

The full code for the History class is here (http://pastebin.com/ZGKK2V84).

Answer 1

Although this question is a little vague, in general, with a class like this, I would propose testing the following, at a minimum:

• Test each method and property in your public API, verifying that each changes the internal collections appropriately when adding “real” data
• Test adding invalid data to each method (should this accept null references, for example?), making sure you either get appropriate exceptions or the behavior you desire
• Given it’s a generic class, I would test this with both a value type and a reference type (unless you decide to add a constraint to one or the other)