From kde-panel-devel Mon Jul 28 13:46:56 2014 From: Aleix Pol Date: Mon, 28 Jul 2014 13:46:56 +0000 To: kde-panel-devel Subject: Re: Using more of our CI, Coverage and cppcheck Message-Id: X-MARC-Message: https://marc.info/?l=kde-panel-devel&m=140655525011264 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============2501956481221929363==" --===============2501956481221929363== Content-Type: multipart/alternative; boundary=047d7bf15e9e3a474604ff41299d --047d7bf15e9e3a474604ff41299d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Sun, Jul 27, 2014 at 11:59 PM, =C3=80lex Fiestas wrot= e: > 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 mig= ht > need special love. > > http://build.kde.org/job/plasma-framework_master_qt5/665/Variation=3DAll,= label=3DLINBUILDER/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=3DAll,= label=3DLINBUILDER/cppcheckResult/ > > If you want to enable it in more projects, look at: > > https://techbase.kde.org/Development/Tutorials/Unittests#Coverage_tools_a= nd_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=3Dwebsites%2Fbuild-kde-org. [DEFAULT] configureExtraArgs=3D-DBUILD_COVERAGE=3DON --047d7bf15e9e3a474604ff41299d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On S= un, Jul 27, 2014 at 11:59 PM, =C3=80lex 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 addin= g
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 m= ight
need special love.
http://build.kde.= org/job/plasma-framework_master_qt5/665/Variation=3DAll,label=3DLINBUILDER/= cobertura/

Also, most projects have cppcheck enabled, this thing is usually right so w= e
want to to make it happy:
http://build= .kde.org/job/plasma-framework_master_qt5/665/Variation=3DAll,label=3DLINBUI= LDER/cppcheckResult/

If you want to enable it in more projects, look at:
https://techbase.kde.org/Development/Tuto= rials/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]=C2=A0And add this option in the configuraiotn of yo= ur CI build: http://quickgit.kde.org/?p=3Dwebsites%2Fbuild-kde-org. [DEFAULT] co= nfigureExtraArgs=3D-DBUILD_COVERAGE=3DON
--047d7bf15e9e3a474604ff41299d-- --===============2501956481221929363== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel --===============2501956481221929363==--