From: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>
To: John Schmitt <marmalodak@gmail.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] coverage history
Date: Mon, 05 Nov 2012 17:15:24 +0100 [thread overview]
Message-ID: <5097E61C.2050100@linux.vnet.ibm.com> (raw)
In-Reply-To: <20121105153358.GI31939@mediapc.snapdragonfly.net>
On 05.11.2012 16:33, John Schmitt wrote:
> On Tue, Oct 30, 2012 at 12:21:49PM +0100, Peter Oberparleiter wrote:
>> On 30.10.2012 01:39, John Schmitt wrote:
>>> Is there a way to generate track the coverage of a project over time? If I'm writing unit tests as my code base expands, can I see how my coverage of that code base goes up or down over time as reported by lcov?
>>
>> There is no integrated way to track coverage changes over time with
>> lcov, although this may be a good idea for a future improvement.
>>
>> For now, you could manually extract the coverage results using the
>> --summary or --list option of lcov and put that into a spreadsheet.
>
> Thank you, Peter, this is the best advice I've received.
You're welcome!
> I see the --list option in lcov but I don't see a --summary. Are you referring to --function-summaries which gcov takes?
The "lcov --summary <filename>" option comes with lcov 1.10. It shows
coverage rates for all of a file, while --list shows the information for
each file.
Regards,
Peter
--
Peter Oberparleiter
Linux on System z Development - IBM Germany
------------------------------------------------------------------------------
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, update software, and manage PCs from one command center
Diagnose problems and improve visibility into emerging IT issues
Automate, monitor and manage. Do more in less time with Central
http://p.sf.net/sfu/logmein12331_d2d
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2012-11-05 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-30 0:39 [LTP] coverage history John Schmitt
2012-10-30 11:21 ` Peter Oberparleiter
2012-11-05 15:33 ` John Schmitt
2012-11-05 16:15 ` Peter Oberparleiter [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5097E61C.2050100@linux.vnet.ibm.com \
--to=oberpar@linux.vnet.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=marmalodak@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox