summaryrefslogtreecommitdiff
path: root/t/README
diff options
context:
space:
mode:
authorLibravatar Michael Witten <mfwitten@gmail.com>2011-02-22 17:15:00 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2011-03-30 11:59:52 -0700
commit63d329459370b09637d49a430f63d3ecd2bc3f25 (patch)
tree1cc2eb113a08476d90af2eff785ae30ff6d3b082 /t/README
parentDocumentation/config.txt: make truth value of numbers more explicit (diff)
downloadtgif-63d329459370b09637d49a430f63d3ecd2bc3f25.tar.xz
Typos: t/README
Signed-off-by: Michael Witten <mfwitten@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/README')
-rw-r--r--t/README9
1 files changed, 4 insertions, 5 deletions
diff --git a/t/README b/t/README
index d44a614ea3..6122a6c733 100644
--- a/t/README
+++ b/t/README
@@ -197,7 +197,7 @@ we are testing.
If you create files under t/ directory (i.e. here) that is not
the top-level test script, never name the file to match the above
pattern. The Makefile here considers all such files as the
-top-level test script and tries to run all of them. A care is
+top-level test script and tries to run all of them. Care is
especially needed if you are creating a common test library
file, similar to test-lib.sh, because such a library file may
not be suitable for standalone execution.
@@ -281,9 +281,8 @@ Do:
- Check the test coverage for your tests. See the "Test coverage"
below.
- Don't blindly follow test coverage metrics, they're a good way to
- spot if you've missed something. If a new function you added
- doesn't have any coverage you're probably doing something wrong,
+ Don't blindly follow test coverage metrics; if a new function you added
+ doesn't have any coverage, then you're probably doing something wrong,
but having 100% coverage doesn't necessarily mean that you tested
everything.
@@ -427,7 +426,7 @@ library for your script to use.
- test_tick
Make commit and tag names consistent by setting the author and
- committer times to defined stated. Subsequent calls will
+ committer times to defined state. Subsequent calls will
advance the times by a fixed amount.
- test_commit <message> [<filename> [<contents>]]