Note that there are some explanatory texts on larger screens.

plurals
  1. POPartCover generates empty output file
    primarykey
    data
    text
    <p>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:</p> <pre><code>&lt;!-- UnitTest Configuration --&gt; &lt;!-- ====================== --&gt; &lt;!-- This configuration runs the tests through Gallio with MbUnit together with PartCover to get the results of the test together with the coverage results --&gt; &lt;target name="unitTest"&gt; &lt;echo message="Unittesting ${AssemblyToTest}"/&gt; &lt;exec program="${Paths.Tools}\PartCover\Partcover.exe" failonerror="true"&gt; &lt;arg line="--target &amp;quot;${Paths.Tools}\Gallio\Gallio.Echo.exe&amp;quot;" /&gt; &lt;arg line="--target-work-dir ${AssemblyToTestLocation}"/&gt; &lt;arg line="--target-args /r:Local &amp;quot;${AssemblyToTest}&amp;quot;" /&gt; &lt;arg line="--include &amp;quot;[${Tests.TestedAssemblyName}]*&amp;quot;" /&gt; &lt;arg line="--output ${Paths.Output}\Coverage.xml" /&gt; &lt;/exec&gt; &lt;/target&gt; </code></pre> <p>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.</p> <p>Output of the variables:-</p> <ul> <li>${Paths.Tools} : C:\Robinson\Trunk\ </li> <li>${Tests.TestedAssemblyName} : Name of the DLL</li> <li>${AssemblyToTestLocation} : Path to the DLL</li> </ul> <p>Am I missing something?</p> <p><em><strong>EDIT</em></strong> 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.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload