Question

我正在尝试使用NUnit设置MSBuild作为单元测试驱动程序但是在NUnit完成后脚本会一直挂起。它似乎没有完成它的工作，让MSBuild继续工作我正在使用.NET 4.0并使用NUnit 2.5.8 如果我手动或使用gui（VS2010或NUnit）运行测试，它可以正常工作，但在MSBuild调用时则不行。

我很感激任何寻找错误的帮助，或者只是想知道在哪里寻找答案。

手动命令如下所示：
C：\ ....＆gt; nunit \ nunit-console.exe buildbinaries \ YYYY.XXXX.Extractor.Test.IntegrationTest.dll /xml=nunit.xml

和缩写为MSBuild：

  <Import Project="$(MSBuildBinPath)\Microsoft.CSharp.targets" />

  <!-- define folders for build output and reports -->
  <PropertyGroup>
    <BuildPath>buildbinaries\</BuildPath>
    <ReportPath>buildreports\</ReportPath>
    <ReleaseFolder>release_artefacts\</ReleaseFolder>
    <PublishFolder>c:\ZZZ Applications\published builds\</PublishFolder>
    <DeploymentFolder>\\seldclq99\ZZZ_Costanza_Dev$\</DeploymentFolder>
  </PropertyGroup>

  <PropertyGroup>
    <!-- specify assemblies that should be included in coverage report -->
    <NCoverAssemblyList>YYYY.XXXX.Extractor.Business.dll; YYYY.XXXX.Extractor.Common.dll YYYY.XXXX.Extractor.Configuration.dll YYYY.XXXX.Extractor.DAL.Access.dll YYYY.XXXX.Extractor.DAL.Facade.dll YYYY.XXXX.Extractor.Service.Contracts.dll YYYY.XXXX.Extractor.Service.dll YYYY.XXXX.Extractor.Service.Host.WebHost.dll YYYY.XXXX.Extractor.ServiceGateway.dll</NCoverAssemblyList>
  </PropertyGroup>

  <!-- define item group for deliverables -->
  <ItemGroup>
    <Binaries Include="$(BuildPath)/**/*.*" Exclude="$(BuildPath)nunit*" />
  </ItemGroup>

  <!--
  This is the default target that will be executed if MSBuild is not started
  with a specific target (this is decided by the DefaultTargets attribute in
  the root element of this XML document)
  -->
  <Target Name="BuildAndTest">
    <CallTarget Targets="SetupDirs" />
    <CallTarget Targets="Build" />
    <CallTarget Targets="UnitAndIntegrationTest" />
    <CallTarget Targets="FxCop" />
    <CallTarget Targets="CopyToReleaseFolder" />
  </Target>

  <!-- Setup folders used during the build -->
  <Target Name="SetupDirs">
    <RemoveDir Directories="$(ReportPath);$(BuildPath);$(ReleaseFolder)" ContinueOnError="true"/>
    <MakeDir Directories="$(ReportPath);$(BuildPath);$(ReleaseFolder);$(AssemblyVersionFolder)" ContinueOnError="true"/>
  </Target>

  <Target Name="Build">
    <!-- build the software using msbuild -->
    <!-- Build error in the Install build-->
    <MSBuild ContinueOnError="true" RebaseOutputs="false" Targets="Clean;Rebuild" Projects="YYYYXXXXExtractor.sln" Properties="Configuration=Release;OutDir=..\$(BuildPath)" />

  </Target>

  <!--Run the coverage stats-->
  <Target Name="UnitAndIntegrationTest">
      <Exec Command="nunit\nunit-console.exe buildbinaries\YYYY.XXXX.Extractor.Test.IntegrationTest.dll /xml=$(ReportPath)nunit.xml "/>
      <CallTarget Targets="UnitTest" />
  </Target>

  <Target Name="UnitTest">
      <Exec Command="nunit\nunit-console.exe buildbinaries\YYYY.XXXX.Extractor.Test.UnitTest.dll /xml=$(ReportPath)nunit.xml"/>
  </Target>

  <!-- Run FxCop  -->
  <!-- The ForceError.bat fires if the xml file is not found... aka an error was found -->
  <!-- The quiet command forces an Xml file ONLY if warnings or Errors are found -->
  <Target  Name="FxCop">
    <Exec  Command="..\tools\fxcop\FxCopCmd.exe /p:..\FxCopSettings.FxCop /o:$(ReportPath)fxcop.xml" />
    <Exec Condition="Exists('$(ReportPath)fxcop.xml')" Command="..\tools\fxcop\FX_Cop_Failed_Rule_Checks.bat" />

    <!--STATS: Run again but don't fail and this time run for all rules.-->
    <Exec  Command="..\tools\fxcop\FxCopCmd.exe /p:..\FxCopSettingsALLRULES.FxCop /o:$(ReportPath)fxCopAllRules.xml" />

  </Target >

Answer 1

我在使用NUnit 2.5.8时遇到了同样的问题。在nunit网站上有一些关于测试过程悬挂的讨论。我切换到NUnit 2.5.7，问题就消失了。

这似乎是几周前在2.5.9修复的。

Answer 2

自从升级到.NET 4以来，我注意到在构建服务器上的类似行为.MsBuild似乎间歇性地挂在NUnit，FxCop或Dotcover EXEC命令上。如果检查任务管理器，外部执行的命令（例如Nunit.exe）的进程仍然存在。如果你手动杀死进程，MsBuild继续它的快乐方式 - 这远非理想！

这可能是最新版本的MsBuild中的错误吗？我们的构建服务器运行得非常愉快，直到.NET 4升级。

Answer 3

如果您在服务器上运行ProcessExplorer，您会注意到产生了一个名为nunit-agent的带外进程，最终阻止了nunit runner。

我没有验证这在2.5.9中是否已修复，但它可能是一些可能有用的信息。

NUnit完成后，MSBuild挂起

3 个答案: