I'm curious about the test coverage some of the listings. There's 100%
coverage of src/pmc/compiler.pmc but 12.5% coverage of
src/pmc/compiler.c which is created from compiler.pmc. With the
inheritence of pmc's, won't that screw with the coverage reports as
well?
But, as a side note, when I'm working on jit, it would be very helpful
to run `make testj` or whatever and know what's being covered and what
isn't. I have had at least one instance where one or two tests
revealed an error on my part because that part of code was never
touched. What would be needed(on freebsd) to get a personal test
coverage?
On Sep 15, 2007, at 10:12 AM, Paul Cochrane wrote:
Hi everyone,
I finally managed to get the 'make cover' target working so that we
can now see the test coverage of the C-language parts of Parrot.
kid51++ (Jim Keenan) has been kind enough to give me space on his web
server to put the current coverage results, which you can find here:
http://thenceforward.net/parrot/coverage/c-components/coverage.html
(or by following the Code Coverage link on the Parrot Wiki).
This is, incidentally, where the Perl-language configuration and build
test coverage is hosted.
We're currently at 42% coverage :-( (this is on by Gentoo Linux x86
machine, YMMV). At least we now know where effort can be put to
improve things :-)
Anyway, have fun, and a good weekend!
Paul
