A Good Test

Need a good test for your database application? Take your database server offline. While it's off, write some unit tests and then see how your application is doing. There are a lot of things you may not have realized but thought were OK. For example, does it really need to throw an exception? Does your application's last line of defense (e.g. OnThreadException in .NET) really need to kick in to handle these problems? Shouldn't your program let people work disconnected anyway? Of course I'm raising this issue because our database server is down right now :)