How should I unit-test a simple CRUD-class?

Question

I am right now trying to do very, very simple stuff with unit-testing in VS2008, to get started and get a feel for this. I think I have testing of small non-database stuff down,

Answer 1

I find that it works best to do basically what you've outlined. However, rather than splitting the create event up into each operation, I tend to create a single record in one method but store the id value of that record in a private class variable, then I fetch it back (read) inside of each method. So, then I have a Read assert method, then another Update assert method, and finally a Delete assert method.

Though, what you've outlined above is very thorough. The biggest problem though, is if your delete method fails in your read assert method, then you could be mislead into believing that your read functionality is broken when in fact it is the delete functionality is deleted.