Hi
just to get things straight : you have 1 CCNet project with the following task section (sort of): <tasks> <devenv .. /> <TMockRunner /> <nunit .. /> </tasks> now I suppose you call the Tmockrunned via the exec task, since it is not naticely supported in CCNet. and you run Nunit via the NUinit task or the exec task, correct? now it is possible, if you do the following place the TMockrunner and the Nunit inside a build script Nant, MSbuild, ... (you can even place the compile in it if you want) in Nant you can execute TMockRunner, and set the failonerror attribute to false, so when there is an error, it will still execute NUnit see the page below for an example http://confluence.public.thoughtworks.org/display/CCNET/Using+CruiseControl.NET+with+NUnit wiht kind regards Ruben Willems On Thu, Feb 12, 2009 at 8:56 AM, Mikko Rasinkangas <[email protected]>wrote: > > Hi. > > I have a question regarding using TypeMock and NUnit with > CruiseControl. > > Since TypeMock enabling in CruiseControl requires the usage of the > <TMockRunner> element, doesn't it basically prevent execution of both > typemocked and non-typemocked test cases if either the <TMockRunner> > or <nunit> tasks fails? > > Example of a CruiseControl.net script: > > <devenv> > ... > </devenv> > > <TMockRunner> > ... type mocked test cases executed by this > </TMockRunner> > > <nunit> > ... normal test cases executed by this > </nunit> > > So, if for example the test cases executed inside the <TMockRunner> > task fail, it means that the test cases in the <nunit> task won't be > executed, right? > > Is there any way get both <TMockRunner> and <nunit> test case tasks to > be executed always and the total outcome of those two tasks determine > if the next task should be executed. > > Hmm... I wonder if that was clear enough... > > > -Mikko
