Was out and about, and saw a post over on Barry Gervin's blog about a new nunit.  I've been doing more and more with nunit, staring at (hopefully) green lines all day long.  Can't wait to dive into some of this.  Categories seem very nice, as well as the explicit feature. 

I also have some ideas on an nunit addon for easing database development testing.  Some of the things that come to mind are
DBAssert.IsEqual(tablename,whereconditions(),fieldvaluetomatch)
Attributes for sprocs or inline sql to run on the way in, and out of a method
DB.Run(ArbitrarySql)

Amongst some others that I will gather and post.  In my head, I see DB testing as a huge hole in nunit, that could be rather simply solved.  Making it easy to check db values, and abstract some basic DB operations in your unit tests would really help alot.  Of course I don't expect any of these ideas to be the holy grail of DB unit testing, but would at least help in the projects I have been on.  Just even a simple way to check that any given CRUD operation succeeded or failed would help for the majority of DB unit testing.  Anyone had any thoughts on db testing?

Get the latest nunit here.