开发者

PartCover generates empty output file

开发者 https://www.devze.com 2023-03-13 16:35 出处:网络
I\'m currently trying to create a Nant task for our TeamCity setup so that our UnitTests are ran through Gallio and covered by PartCover. The task looks like this:

I'm currently trying to create a Nant task for our TeamCity setup so that our UnitTests are ran through Gallio and covered by PartCover. The task looks like this:

<!-- UnitTest Configuration -->
  <!-- ====================== -->
  <!-- This configuration runs the tests through Gallio with MbUnit together with
       PartCover开发者_运维技巧 to get the results of the test together with the coverage results 
  -->
  <target name="unitTest">      
        <echo message="Unittesting ${AssemblyToTest}"/>
        <exec program="${Paths.Tools}\PartCover\Partcover.exe" failonerror="true">
          <arg line="--target &quot;${Paths.Tools}\Gallio\Gallio.Echo.exe&quot;" />
          <arg line="--target-work-dir ${AssemblyToTestLocation}"/>
          <arg line="--target-args /r:Local &quot;${AssemblyToTest}&quot;" />
          <arg line="--include &quot;[${Tests.TestedAssemblyName}]*&quot;" />
          <arg line="--output ${Paths.Output}\Coverage.xml" />
        </exec>
  </target>

The tests are running, we can see this in TeamCity, and a Coverage.xml file is generated, but empty. There's only a single line in it.

Output of the variables:-

  • ${Paths.Tools} : C:\Robinson\Trunk\
  • ${Tests.TestedAssemblyName} : Name of the DLL
  • ${AssemblyToTestLocation} : Path to the DLL

Am I missing something?

EDIT The TeamCity application is running on a Windows Server 2003 R2 Server, and all the build-agents performing the work are currently running on Windows XP Systems, all 32bit installations.


I believe we covered this issue in https://github.com/sawilde/partcover.net4/issues/46

and the solution was along the lines of

--include [${Tests.TestedAssemblyName}*]* ?

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号