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

List:       kde-panel-devel
Subject:    Re: Using more of our CI, Coverage and cppcheck
From:       Aleix Pol <aleixpol () kde ! org>
Date:       2014-07-28 13:46:56
Message-ID: CACcA1Rpi3-h-0kyBoKgmOROJnLXbzqfi3im44zNCvT5mRyq2UA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Sun, Jul 27, 2014 at 11:59 PM, Àlex Fiestas <afiestas@kde.org> wrote:

> Hi there!
>
> During this weekend Ben and I have enabled the code-coverage in plasma-
> framework, my personal idea is to enable it in most projects.
>
> We should not go loco with code coverage, we stand where we stand and
> adding
> test non-stop will not fix anything. What we can do though is use this
> tool to
> make sure we don't make the situation worse, and to check which parts might
> need special love.
>
> http://build.kde.org/job/plasma-framework_master_qt5/665/Variation=All,label=LINBUILDER/cobertura/
>
> Also, most projects have cppcheck enabled, this thing is usually right so
> we
> want to to make it happy:
>
> http://build.kde.org/job/plasma-framework_master_qt5/665/Variation=All,label=LINBUILDER/cppcheckResult/
>
> If you want to enable it in more projects, look at:
>
> https://techbase.kde.org/Development/Tutorials/Unittests#Coverage_tools_and_CI
>
> Cheers!
>

Looks interesting, lots of work to be done :).

From the wiki: [1]
Do we need special powers to change these?

Aleix

[1] And add this option in the configuraiotn of your CI build:
http://quickgit.kde.org/?p=websites%2Fbuild-kde-org. [DEFAULT]
configureExtraArgs=-DBUILD_COVERAGE=ON

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sun, Jul 27, 2014 \
at 11:59 PM, Àlex Fiestas <span dir="ltr">&lt;<a href="mailto:afiestas@kde.org" \
target="_blank">afiestas@kde.org</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi \
there!<br> <br>
During this weekend Ben and I have enabled the code-coverage in plasma-<br>
framework, my personal idea is to enable it in most projects.<br>
<br>
We should not go loco with code coverage, we stand where we stand and adding<br>
test non-stop will not fix anything. What we can do though is use this tool to<br>
make sure we don&#39;t make the situation worse, and to check which parts might<br>
need special love.<br>
<a href="http://build.kde.org/job/plasma-framework_master_qt5/665/Variation=All,label=LINBUILDER/cobertura/" \
target="_blank">http://build.kde.org/job/plasma-framework_master_qt5/665/Variation=All,label=LINBUILDER/cobertura/</a><br>



<br>
Also, most projects have cppcheck enabled, this thing is usually right so we<br>
want to to make it happy:<br>
<a href="http://build.kde.org/job/plasma-framework_master_qt5/665/Variation=All,label=LINBUILDER/cppcheckResult/" \
target="_blank">http://build.kde.org/job/plasma-framework_master_qt5/665/Variation=All,label=LINBUILDER/cppcheckResult/</a><br>



<br>
If you want to enable it in more projects, look at:<br>
<a href="https://techbase.kde.org/Development/Tutorials/Unittests#Coverage_tools_and_CI" \
target="_blank">https://techbase.kde.org/Development/Tutorials/Unittests#Coverage_tools_and_CI</a><br>
 <br>
Cheers!<br></blockquote><div><br></div><div>Looks interesting, lots of work to be \
done :).</div><div><br></div><div>From the wiki: [1]</div><div>Do we need special \
powers to change these?</div><div><br></div><div>Aleix</div>

<div><br></div><div>[1]  And add this option in the configuraiotn of your CI build: \
<a href="http://quickgit.kde.org/?p=websites%2Fbuild-kde-org">http://quickgit.kde.org/?p=websites%2Fbuild-kde-org</a>. \
[DEFAULT] configureExtraArgs=-DBUILD_COVERAGE=ON</div>

</div></div></div>



_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


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