Using more of our CI, Coverage and cppcheck

[Aleix Pol]

On Sun, Jul 27, 2014 at 11:59 PM, Àlex Fiestas <afiestas at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20140728/8e71298c/attachment-0001.html>