I have to create the plan each time. I have to assign contacts to the plan. They have to request sign off in order to be able to sign it off.I raise exceptions if any of the above is not the case if a sign off is requested and all is not good. I also want to create and delete the plan from the database on each unit test. Emails get sent out etc. which I am able to mock. Maybe I could mock the db interaction but I need to create more interfaces needlessly for that then. I am recreating all the steps if I split it into smaller tests. I have created a heap of sh*! that has just banged everything together. Not sure if there is a better way. [EMAIL PROTECTED]
> Date: Fri, 4 Jan 2008 10:59:13 -0500> From: [EMAIL PROTECTED]> Subject: Re: > [ADVANCED-DOTNET] Unwiedly unit test> To: > ADVANCED-DOTNET@DISCUSS.DEVELOP.COM> > On Fri, 4 Jan 2008 16:03:37 +0000, > Paul Cowan <[EMAIL PROTECTED]> wrote:> > >I am but it is getting the > structure into the state where I can test the> sign off process.> > That > should be part of the setup. But, you've got more than simply setup> in > there, for example, you're also testing invalid login.> > >> >If I split it > up into smaller tests then I still have to go through the> same routine for > each smaller test which will take more time.> > What else, besides sign off, > needs a signed-on state?> > ===================================> This list is > hosted by DevelopMentor® http://www.develop.com> > View archives and manage > your subscription(s) at http://discuss.develop.com _________________________________________________________________ Who's friends with who and co-starred in what? http://www.searchgamesbox.com/celebrityseparation.shtml =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
