From 681186ae3ab340dd684b1d9e09b457baeb2331f9 Mon Sep 17 00:00:00 2001 From: Mathias Lafeldt Date: Wed, 9 Mar 2011 21:25:09 +0100 Subject: Fix typo in t/README Signed-off-by: Mathias Lafeldt Signed-off-by: Junio C Hamano --- t/README | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 't/README') diff --git a/t/README b/t/README index 25f7d2d2e3..78c9e6575c 100644 --- a/t/README +++ b/t/README @@ -328,7 +328,7 @@ Keep in mind: Skipping tests -------------- -If you need to skip tests you should do so be using the three-arg form +If you need to skip tests you should do so by using the three-arg form of the test_* functions (see the "Test harness library" section below), e.g.: -- cgit v1.2.3 From 0986de94f942d889622e6cfe55b565ea9519826b Mon Sep 17 00:00:00 2001 From: Piotr Krukowiecki Date: Tue, 15 Mar 2011 20:58:14 +0100 Subject: Documentation: running test with --debug keeps "trash" directory Signed-off-by: Piotr Krukowiecki Signed-off-by: Junio C Hamano --- t/README | 4 ++++ 1 file changed, 4 insertions(+) (limited to 't/README') diff --git a/t/README b/t/README index 78c9e6575c..165e7cf34d 100644 --- a/t/README +++ b/t/README @@ -79,6 +79,10 @@ appropriately before running "make". --debug:: This may help the person who is developing a new test. It causes the command defined with test_debug to run. + The "trash" directory (used to store all temporary data + during testing) is not deleted even if there are no + failed tests so that you can inspect its contents after + the test finished. --immediate:: This causes the test to immediately exit upon the first -- cgit v1.2.3 From 9aec68d3ea935fcb778a3580d950cf20d5bd35f6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Carlos=20Mart=C3=ADn=20Nieto?= Date: Tue, 15 Mar 2011 10:32:11 +0100 Subject: t/README: Add a note about running commands under valgrind MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The test suite runs valgrind with certain options activated. Add a note saying how to run commands under the same conditions as the test suite does. Signed-off-by: Carlos Martín Nieto Signed-off-by: Junio C Hamano --- t/README | 7 +++++++ 1 file changed, 7 insertions(+) (limited to 't/README') diff --git a/t/README b/t/README index 78c9e6575c..d44a614ea3 100644 --- a/t/README +++ b/t/README @@ -98,6 +98,13 @@ appropriately before running "make". not see any output, this option implies --verbose. For convenience, it also implies --tee. + Note that valgrind is run with the option --leak-check=no, + as the git process is short-lived and some errors are not + interesting. In order to run a single command under the same + conditions manually, you should set GIT_VALGRIND to point to + the 't/valgrind/' directory and use the commands under + 't/valgrind/bin/'. + --tee:: In addition to printing the test output to the terminal, write it to files named 't/test-results/$TEST_NAME.out'. -- cgit v1.2.3 From 63d329459370b09637d49a430f63d3ecd2bc3f25 Mon Sep 17 00:00:00 2001 From: Michael Witten Date: Tue, 22 Feb 2011 17:15:00 +0000 Subject: Typos: t/README Signed-off-by: Michael Witten Signed-off-by: Junio C Hamano --- t/README | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) (limited to 't/README') 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 [ []] -- cgit v1.2.3