I agree. Wrapping your library for testing is really pushing the boundaries of sensibility. Low density code that doesn't provide application logic is one of m

I agree. Wrapping your library for testing is really pushing the boundaries of sensibility. Low density code that doesn't provide application logic is one of my pet peeves. There is a philosophy that started in the 90s (and Microsoft was proponent of it [1]) that adding more layers to an application would make it more malleable, but in a typical CRUD web app, layers only bloat the code and make it slower. I'd suspect adding a wrapper to a date class just for the sake of testing is more likely to add bugs than remove them. [1] http://www.asp.net/web-forms/tutorials/data-access/introduction/creating-a-data-access-layer-cs http://www.asp.net/web-forms/tutorials/data-access/introduct...