projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 0c35754) | patch
t/README: Add a note about the dangers of coverage chasing
authorÆvar Arnfjörð Bjarmason <avarab@gmail.com>
Sun, 25 Jul 2010 19:52:45 +0000 (19:52 +0000)
committerJunio C Hamano <gitster@pobox.com>
Wed, 18 Aug 2010 19:42:37 +0000 (12:42 -0700)
commite8b55f5c58d1d9e5d5cd5b24d96b7d3b51047440
tree720e97e77643c37503ae915eb4747b1ad2aa4611tree | snapshot
parent0c357544b0d4415c464fb8b35593b21db1d1f7f7commit | diff
t/README: Add a note about the dangers of coverage chasing

Having no coverage at all is almost always a bad sign, but trying to
attain 100% coverage everywhere is usually a waste of time. Add a
paragraph to explain this to future test writers.

Inspired-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Reviewed-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
t/README diff | blob | history
Git—the stupid content tracker