Chris,

Thanks for getting back, using mstest 2008.  And I have already included the
log files in the merge log path.  I log mstest results to .xml files to a
preset log directory, then include the path as noted below.  Further
insights and/or examples are appreciated.



 <publishers>
      <merge>
        <files>

<file>C:\TEMP\logs\BuildLogs\ccnet\fwe_unit_test-ci\latest\*.log</file>

<file>C:\TEMP\logs\BuildLogs\ccnet\fwe_unit_test-ci\latest\*.err</file>
*          <file>O:\Project\TestResults\*.xml</file>*
        </files>
      </merge>
      <xmllogger />
      <statistics />
      <modificationHistory onlyLogWhenChangesFound="true" />




On Wed, Feb 10, 2010 at 12:43 PM, Christophe Planty <
[email protected]> wrote:

> There's 2 kind of MStest file , and 2 possible xsl transforms .
> mstest 2005 or 2008.
> There's some templates around, but i must search for it :)
>
> also ensure that the file is in the directory you've defined (artefact one?
> - as by default mstest does store result in a new subfolder)  and that your
> project configuration does merge this file (on the publisher block).
>
> <
> merge><files> <file>PathToTerstResults\*.trx</file></files></merge>
>
> /Chris
>
>
> On Wed, Feb 10, 2010 at 9:22 PM, mac taylor <[email protected]> wrote:
>
>> I have tried multiple links to integrate MSTest results onto the Cruise
>> Control server output section.  It appears the .xsl stylesheets in the
>> CC.NET <http://cc.net/> server are not capable.  Does anyone have
>> successful MSTest integration with CC.NET <http://cc.net/>?  The version
>> is old (1.4.0.3524) however the research insists this is not the issue.  Any
>> assistance is highly appreciated.
>>
>>
>> MT
>>
>>
>

Reply via email to