My company recently wrote a very complex scheduling module for booking appointments online through a DotNetNuke module. We are using a highly modified version of the Infragistics WebSchedule controls to complete this. I am currently refactoring the code so we can write unit tests against some of our event handlers that are causing logic problems. For instance, a WebControl in MyView.ascx has an event handler ActivityAdding. I have added this method to a new class called WebScheduleEventHandlers. That class uses the static class ScheduleController to call into the data layer - very similar to the UserController class.

My problem now is that I have no way to test this new class without putting data into the database first. I want my unit tests to run without having to first load the database. I wrote unit tests for the data provider (SqlDataProvider) class itself.

Can anyone suggest a better way to design modules so that the business logic is more easily tested in isolation, and the data layer can be mocked to produce the desired data?

Thanks in Advance,

Ben