On 1/26/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Joe Neeman escreveu:
>
> I have all the page-breaking files with coverage around 90% now, but
> I'll try to improve it a bit more (btw, the reason
> page-turn-page-breaking.cc was so low is that I forgot to put a \book
> around the regressi
Joe Neeman escreveu:
>
> I have all the page-breaking files with coverage around 90% now, but
> I'll try to improve it a bit more (btw, the reason
> page-turn-page-breaking.cc was so low is that I forgot to put a \book
> around the regression tests so the lilypond-book output skipped the
> page-br
On 1/2/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Hi,
I've been running coverage tests of the input/regression/ suite, to
see which parts of the code are not excercised. This has already
turned up some bugs.
You can get a full overview by running buildscripts/build-coverage.sh,
but here
Joe Neeman escreveu:
> Sure. I assume the first number is the percentage of lines covered in
> that file, but what does (lines) mean?
number of covered lines in the file, I think.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Musi
On 1/2/07, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Hi,
I've been running coverage tests of the input/regression/ suite, to
see which parts of the code are not excercised. This has already
turned up some bugs.
You can get a full overview by running buildscripts/build-coverage.sh,
but here
Hi,
I've been running coverage tests of the input/regression/ suite, to
see which parts of the code are not excercised. This has already
turned up some bugs.
You can get a full overview by running buildscripts/build-coverage.sh,
but here are some interesting offenders
cov % ( lines): file
---
