This Question is Possibly Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)
3 Replies Last post: Jul 4, 2014 11:13 AM by Maria Serebryansky  
RC1971 Newbie 12 posts since
Nov 12, 2012
Currently Being Moderated

Jun 26, 2014 8:45 PM

running dotcover from VS2013 IDE vs command line produce different results

When I try to run dotcover using VS2013 IDE the report generated is different compared to when being ran from a command line.  Why is this happening?

 

 

This is part of my msbuild script

 

<LocalDrive Condition="'$(LocalDrive)'==''">E:\</LocalDrive>
<BuildFolder Condition="'$(BuildFolder)'==''">$(LocalDrive)BCS</BuildFolder>
<VSPath Condition="'$(VSPath)'==''">C:\Program Files (x86)\Microsoft Visual Studio 12.0</VSPath>

 

<DotCoverResultsPath Condition="'$(DotCoverResultsPath)'==''">$(MSBuildProjectDirectory)\dotCover</DotCoverResultsPath>
<DotCoverOutDir Condition="'$(DotCoverOutDir)'==''">$(MSBuildProjectDirectory)\CodeQuality\dotCover</DotCoverOutDir>
<DotCoverSnapshotDir Condition="'$(DotCoverSnapshotDir)'==''">$(LocalDrive)Apps\DotCover\snapshot</DotCoverSnapshotDir>
<DotCoverPath Condition="'$(DotCoverPath)'==''">$(JenkinsWSPath)\ZipResult\DotCoverLogZip</DotCoverPath>
<dotCoverExePath Condition="'$(dotCoverExePath)'==''">$(LocalDrive)Program Files (x86)\JetBrains\dotCover\v2.7\Bin\dotCover.exe</dotCoverExePath>

 

<VSTestResultsPath Condition="'$(VSTestResultsPath)'==''">$(MSBuildProjectDirectory)\TestResults</VSTestResultsPath>
<MsTestPath Condition="'$(MsTestPath)'==''">$(VSPath)\Common7\IDE\CommonExtensions\Microsoft\TestWindow\vstest.console.exe</MsTestPath>
<MsTestResultPath Condition="'$(MsTestResultPath)'==''">$(VSPath)\Common7\IDE\TestResults</MsTestResultPath>

 

<Target Name="integration" >
    <ItemGroup>
        <TestAssemblies Include="$(BuildFolder)\Main\Dev\bin\*.Tests.Integration.dll"/>
    </ItemGroup>
   
    <!--<Target Name="integration">-->
    <!-- Call CheckOneAssemblyFile foreach file in TestAssemblies -->
    <MSBuild Projects="$(MSBuildProjectFile)"
        Properties="CurrAssemblyFile=%(TestAssemblies.FileName);CurrAssemblyFullPath=%(TestAssemblies.FullPath);TestResPath=$(DotCoverResultsPath);DCoverOutDir=$(DotCoverOutDir);CtOnErr=$(ContOnError);

        DCoverSSDir=$(DotCoverSnapshotDir)"  Targets="CheckOneAssemblyFile">
    </MSBuild>
</Target>

 

<Target Name="CheckOneAssemblyFile">
    <PropertyGroup>
        <TestAssembliesName>"$(CurrAssemblyFile.Replace(".Tests.Integration",""))"</TestAssembliesName>
    </PropertyGroup>

 

    <!-- This will produce an htm output -->
    <Message Text="Perform coverage analysis" Importance="high"/>

 

    <Exec Command='"$(MsTestPath)" "$(CurrAssemblyFullPath)" /Settings:&quot;$(BuildFolder)\Main\Dev\local.testsettings&quot; /Logger:TRX /framework:Framework45 /platform:x64 /inIsolation' ContinueOnError='$(CtOnErr)'/>

 

</Target>

Maria Serebryansky Newbie 20 posts since
May 15, 2014
Currently Being Moderated
Jun 30, 2014 9:48 PM in response to: RC1971
Re: running dotcover from VS2013 IDE vs command line produce different results

Hello,

 

Could you please clarify what the difference between the two reports is?

 

Kind regards,
Maria

Maria Serebryansky Newbie 20 posts since
May 15, 2014
Currently Being Moderated
Jul 4, 2014 11:13 AM in response to: RC1971
Re: running dotcover from VS2013 IDE vs command line produce different results

I didn’t get your screenshots. Could you please upload them to our ftp server: ftp://ftp.intellij.net/.uploads/ ?

 

Kind regards,
Maria

More Like This

  • Retrieving data ...