[riot-devel] Unit test code coverage using gcov

Bas Stottelaar basstottelaar at gmail.com
Tue Oct 9 16:46:10 CEST 2018


I have been using gcov to visualize my coverage for the KNX tests. I did it
from the command line, so no Makefile hacking, and only for native. Can
share my commands that I have been using.

Kind regards,

Bas Stottelaar



Op di 9 okt. 2018 om 16:26 schreef Martine Lenders <mail at martine-lenders.eu
>:

> Hi,
>
> as there is some discussion to split the unittests into several
> applications [1] and some stuff isn't included into them for good reasons
> (driver test e.g.), I'm not sure if this should be constrained to unittests
> (though they are indeed a good starting point).
>
> Regards,
> Martine
>
> PS: I'm not aware of work going into that direction, so +1 in general.
>
> [1] https://github.com/RIOT-OS/RIOT/issues/8941
>
> Am Di., 9. Okt. 2018 um 16:17 Uhr schrieb STEGEN Toon <
> tstegen at nalys-group.com>:
>
>> Hi Guys,
>>
>>
>> Has anybody succeeded in getting gcov to work to check code coverage of
>> the unit tests?
>>
>> We will try to add support for this, but I want to make sure we're not
>> spending our time on unnecessary work.
>>
>>
>> Greets,
>>
>> Toon Stegen
>> _______________________________________________
>> devel mailing list
>> devel at riot-os.org
>> https://lists.riot-os.org/mailman/listinfo/devel
>>
> _______________________________________________
> devel mailing list
> devel at riot-os.org
> https://lists.riot-os.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20181009/6c53c6b7/attachment.html>


More information about the devel mailing list