Am 11.08.20 um 20:03 schrieb Tilman Hausherr:
I've been wondering why the code coverage changes from time to time, like this:
The reasons are not the current problems, it is something with the preflight
subproject, and it happens when the host changes, i.e. that the build starts
clean. I'm not researching this further at this time but wanted to share the
very few things I found out.
Maybe it has something to do with the isator and bavaria files. For a clean
build there aren't any result files and maybe that algorithm needs some sort of
reference measurement before producing any reasonable values for the statistics.
Tilman
PS: our reported code coverage has increased from 45.6 to now 48.1 in six
months. I'd wish this number to be >50. (Our real code coverage is higher, but
each subproject is counted separately)
It's always a good idea to have as much as possible test cases, especially if
one is refactoring a lot like the on demand parser and such things. I'll try to
do my best to support your efforts.
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org
For additional commands, e-mail: dev-h...@pdfbox.apache.org
