From: Thomas Rast <trast@student.ethz.ch>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/8] Support coverage testing with GCC/gcov
Date: Sun, 15 Feb 2009 23:25:37 +0100 [thread overview]
Message-ID: <cover.1234736374.git.trast@student.ethz.ch> (raw)
So I found a new toy to play with ;-)
The first patch adds some Makefile rules to automate coverage testing.
This initially resulted in a list of 497 untested functions. Then I
picked out some easy targets and made patches for them. This shortens
the list by 20.
Note that the rules currently don't consider any of the
subdirectories. I'm not sure if arm, ppc, and compat are worth
considering, but it would at least have been nice to support it for
xdiff. Unfortunately I can't convince the --coverage code to save
results there, so no analysis is possible. (Running gcc 4.3.2 here.)
BTW, I find it a bit scary that fsck (see 5/8) has so few tests, and
even scarier that out of four simple tests I could come up with it
only passes two. Let's hope the other two are unreasonable.
Thomas Rast (8):
Support coverage testing with GCC/gcov
Test that diff can read from stdin
Test diff --dirstat functionality
Test log --graph
Test fsck a bit harder
Test log --decorate
Test rev-list --parents/--children
Test git-patch-id
Makefile | 23 ++++
t/t1450-fsck.sh | 65 +++++++++++
t/t4002-diff-basic.sh | 8 ++
t/t4013-diff-various.sh | 5 +
t/t4013/diff.diff_--dirstat_master~1_master~2 | 3 +
t/t4013/diff.log_--decorate_--all | 34 ++++++
t/t4013/diff.rev-list_--children_HEAD | 7 +
t/t4013/diff.rev-list_--parents_HEAD | 7 +
t/t4202-log.sh | 148 +++++++++++++++++++++++++
t/t4203-patch-id.sh | 38 +++++++
10 files changed, 338 insertions(+), 0 deletions(-)
create mode 100644 t/t4013/diff.diff_--dirstat_master~1_master~2
create mode 100644 t/t4013/diff.log_--decorate_--all
create mode 100644 t/t4013/diff.rev-list_--children_HEAD
create mode 100644 t/t4013/diff.rev-list_--parents_HEAD
create mode 100755 t/t4203-patch-id.sh
next reply other threads:[~2009-02-15 22:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-15 22:25 Thomas Rast [this message]
2009-02-15 22:25 ` [PATCH 1/8] Support coverage testing with GCC/gcov Thomas Rast
2009-02-16 9:39 ` Matthieu Moy
2009-02-16 11:09 ` Thomas Rast
2009-02-15 22:25 ` [PATCH 2/8] Test that diff can read from stdin Thomas Rast
2009-02-15 22:25 ` [PATCH 3/8] Test diff --dirstat functionality Thomas Rast
2009-02-15 22:25 ` [PATCH 4/8] Test log --graph Thomas Rast
2009-02-15 22:25 ` [PATCH 5/8] Test fsck a bit harder Thomas Rast
2009-02-15 22:25 ` [PATCH 6/8] Test log --decorate Thomas Rast
2009-02-15 22:25 ` [PATCH 7/8] Test rev-list --parents/--children Thomas Rast
2009-02-15 22:25 ` [PATCH 8/8] Test git-patch-id Thomas Rast
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=cover.1234736374.git.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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;
as well as URLs for NNTP newsgroup(s).