We run on Windows 2008 R2. Our continuous integration server is CruiseControl 1.6. We run NUnit directly from our MSBuild scripts and under NCover 3.4. Here is how we invoke NUnit outside of NCover:
Executing through NCover is a little more complicated. Our build script creates a temporary NUnit project which is then fed into NCover using the MSBuild task's that ship with NCover.
We get zombie/orphaned nunit-agent.exe processes regardless of how NUnit gets run. We are working around the problem by creating a pre-build target that kills any nunit-agent.exe processes that are misbehaving.
We run on Windows 2008 R2. Our continuous integration server is CruiseControl 1.6. We run NUnit directly from our MSBuild scripts and under NCover 3.4. Here is how we invoke NUnit outside of NCover:
nunit- console. exe Assembly.dll Assembly2.dll /noshadow /framework=4.0 /domain=Single /include="Unit Test" /xml=NUnitResul ts.xml
Executing through NCover is a little more complicated. Our build script creates a temporary NUnit project which is then fed into NCover using the MSBuild task's that ship with NCover.
We get zombie/orphaned nunit-agent.exe processes regardless of how NUnit gets run. We are working around the problem by creating a pre-build target that kills any nunit-agent.exe processes that are misbehaving.