[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sonar-dev
Subject:    Re: [sonar-dev] Integration tests metrics
From:       Fabrice Bellingard <fabrice.bellingard () sonarsource ! com>
Date:       2012-02-24 7:31:13
Message-ID: CA+PhQbswyKmYfdiVJ5x=beAvkGszta7XztsrCvZzf4LPUWd=Kg () mail ! gmail ! com
[Download RAW message or body]

On Thu, Feb 23, 2012 at 22:27, Alexandre Victoor <alexvictoor@gmail.com>wrote:

> Hello
> Indeed there is a bunch of configuration properties that already exist for
> unit tests that should be duplicated for integration tests :
> - test project pattern
> - gallio filter. As with testng/junit4, with dotnet frameworks we can
> categorize test cases using annotations/attributes. In the same test
> project, we could find unit and integration tests.
> - test assemblies
> - report paths (for reuse reports mode)
> - ...
>
> I was thinking using the "it" acronym to keep the configuration keys not
> too long. We would have keys such as
> : 'sonar.donet.visualstudio.it.testProjectPattern',
> 'sonar.gallio.it.reports.path', 'sonar.gallio.it.filter',
> 'sonar.dotnet.it.assemblies'...
>
> Do you think it makes sens ?
>

Yes, that sounds perfect!




> Regards
>
> Alex
>
>
>
>
> On Thu, Feb 23, 2012 at 9:30 AM, Fabrice Bellingard <
> fabrice.bellingard@sonarsource.com> wrote:
>
>> Hi Alex,
>>
>> this is a good question. From what I see in the sonar-jacoco-plugin, it
>> seems that only the it-coverage metrics are filled with results. Si this
>> could be a first step as well for the Gallio plugin.
>>
>> BTW, we haven't talked about that: how do you plan to tell the plugin
>> which tests are UTs and which are ITs? We already have
>> 'sonar.donet.visualstudio.testProjectPattern' to identify which projects
>> contain unit tests, maybe we could have something like
>> 'sonar.donet.visualstudio.integrationTestProjectPattern'? WDYT?
>>
>>
>>
>> Best regards,
>>
>>  *Fabrice BELLINGARD | SonarSource**
>> *http://sonarsource.com
>>
>>
>>
>> On Mon, Feb 20, 2012 at 23:28, Alexandre Victoor <alexvictoor@gmail.com>wrote:
>>
>>> Hello all,
>>> The metrics on integration tests seems to have been moved out from
>>> jacoco to be part of the sonar core metrics. That is really cool and I was
>>> thinking that it was too bad integration stuffs were not implemented for C#
>>> projects.
>>> So I have started to look how the C# gallio plugin could create
>>> integration tests measures and I have realized there are coverage metrics
>>> but no regular test metrics such as number of tests, test success,
>>> execution time and so on... Did I miss something ? Should I mix unit and
>>> integration tests for all non coverage metrics ?
>>> Thanks in advance for your help
>>>
>>> Alex
>>>
>>>
>>>
>>
>

[Attachment #3 (text/html)]

<br><div class="gmail_quote">On Thu, Feb 23, 2012 at 22:27, Alexandre Victoor <span \
dir="ltr">&lt;<a href="mailto:alexvictoor@gmail.com">alexvictoor@gmail.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px \
#ccc solid;padding-left:1ex">

Hello<div>Indeed there is a bunch of configuration properties that already exist for \
unit tests that should be duplicated for integration tests :</div><div>- test project \
pattern</div><div>- gallio filter. As with testng/junit4, with dotnet frameworks we \
can categorize test cases using annotations/attributes. In the same test project, we \
could find unit and integration tests. </div>


<div>- test assemblies</div><div>- report paths (for reuse reports mode)</div><div>- \
...</div><div><br></div><div>I was thinking using the &quot;it&quot; acronym to keep \
the configuration keys not too long. We would have keys such as : \
&#39;sonar.donet.visualstudio.it.testProjectPattern&#39;, \
&#39;sonar.gallio.it.reports.path&#39;, &#39;sonar.gallio.it.filter&#39;, \
&#39;sonar.dotnet.it.assemblies&#39;...</div>


<div><br></div><div>Do you think it makes sens \
?</div></blockquote><div><br></div><div>Yes, that sounds \
perfect!</div><div><br></div><div><br></div><div> </div><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">

<div>Regards</div><div><br></div><div>Alex</div><div class="HOEnZb"><div \
class="h5"><div><br></div><div><br></div><div><br><br><div class="gmail_quote">On \
Thu, Feb 23, 2012 at 9:30 AM, Fabrice Bellingard <span dir="ltr">&lt;<a \
href="mailto:fabrice.bellingard@sonarsource.com" \
target="_blank">fabrice.bellingard@sonarsource.com</a>&gt;</span> wrote:<br>


<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">Hi Alex,<div><br></div><div>this is a good question. From \
what I see in the sonar-jacoco-plugin, it seems that only the it-coverage metrics are \
filled with results. Si this could be a first step as well for the Gallio \
plugin.</div>




<div><br></div><div>BTW, we haven&#39;t talked about that: how do you plan to tell \
the plugin which tests are UTs and which are ITs? We already have \
&#39;sonar.donet.visualstudio.testProjectPattern&#39; to identify which projects \
contain unit tests, maybe we could have something like \
&#39;sonar.donet.visualstudio.integrationTestProjectPattern&#39;? WDYT?</div>




<div><br></div><div><br clear="all"><span \
style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse"><div><br></div><div>Best \
regards,</div><div><br></div><div><table width="100%" border="0" cellspacing="0" \
cellpadding="0" style="color:rgb(34,34,34);font-family:&#39;Times New Roman&#39;">




<tbody><tr><td style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;font-family:arial,sans-serif"></td></tr><tr><td \
style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;font-family:arial,sans-serif">





<div style="font-family:Arial,Helvetica,sans-serif;font-size:12px"><strong>Fabrice \
BELLINGARD | <font color="#C30C00">SonarSource</font></strong><font \
color="#666666"><i><br></i></font><a href="http://sonarsource.com/" \
style="color:rgb(195,12,0)" target="_blank">http://sonarsource.com</a></div>




</td></tr></tbody></table></div></span><div><div><br>
<br><br><div class="gmail_quote">On Mon, Feb 20, 2012 at 23:28, Alexandre Victoor \
<span dir="ltr">&lt;<a href="mailto:alexvictoor@gmail.com" \
target="_blank">alexvictoor@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex">




Hello all,<div>The metrics on integration tests seems to have been moved out from \
jacoco to be part of the sonar core metrics. That is really cool and I was thinking \
that it was too bad integration stuffs were not implemented for C# projects.</div>





<div>So I have started to look how the C# gallio plugin could create integration \
tests measures and I have realized there are coverage metrics but no regular test \
metrics such as number of tests, test success, execution time and so on... Did I miss \
something ? Should I mix unit and integration tests for all non coverage metrics \
?</div>





<div>Thanks in advance for your \
help</div><div><br></div><div>Alex</div><div><br></div><div><br></div> \
</blockquote></div><br></div></div></div> </blockquote></div><br></div>
</div></div></blockquote></div><br>



[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic