|
From: Luigi B. <lui...@gm...> - 2015-09-07 21:24:28
|
Hi Peter,
thanks, it's very interesting. (And not as bad as I thought.)
We'll have to think how to act on the info...
Luigi
On Mon, Sep 7, 2015 at 9:38 PM Peter Caspers <pca...@gm...> wrote:
> Hi Luigi, all,
>
> I ran a code coverage analysis highlighting parts of the library's
> code which are not executed by the test-suite (on the current master).
> You can download the result with (e.g.)
>
> wget -O quantlib_code_coverage.zip
>
> https://github.com/pcaspers/doc/blob/master/quantlib_code_coverage.zip?raw=true
>
> or by entering the url directly into a browser. Then unpack the
> archive and open index.html. There are help pages contained explaining
> the meaning of the numbers and colors used to highlight non-covered
> source code lines. While I do not fully understand all of the dark
> yellow marks yet, the yellow and red ones look plausible and useful.
> As well as the list of totally uncovered files of course.
>
> I thought this could be interesting to share. I created the output
> using the code coverage tool of the Intel C++ compiler 16.0 (which is
> free to use in the context of open source projects).
>
> Thank you
> Peter
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> QuantLib-dev mailing list
> Qua...@li...
> https://lists.sourceforge.net/lists/listinfo/quantlib-dev
>
--
<http://leanpub.com/implementingquantlib/>
<http://implementingquantlib.com>
<http://twitter.com/lballabio>
|