[PATCH 1/3] test-lib: Document short options in t/README
- From
Ilya Bobyr <ilya.bobyr@gmail.com>
- Date
- Apr 22, 2014, 08:19 UTC
- Message-ID
- <1398154767-1276-2-git-send-email-ilya.bobyr@gmail.com>
- In-Reply-To
- <1398154767-1276-1-git-send-email-ilya.bobyr@gmail.com>
Most arguments that could be provided to a test have short forms. Unless documented, the only way to learn them is to read the code.
Signed-off-by: Ilya Bobyr <ilya.bobyr@gmail.com> --- t/README | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/t/README b/t/README index caeeb9d..6b93aca 100644 --- a/t/README +++ b/t/README @@ -71,7 +71,7 @@ You can pass --verbose (or -v), --debug (or -d), and --immediate (or -i) command line argument to the test, or by setting GIT_TEST_OPTS appropriately before running "make". ---verbose:: +-v,--verbose:: This makes the test more verbose. Specifically, the command being run and their output if any are also output. @@ -81,7 +81,7 @@ appropriately before running "make". numbers matching <pattern>. The number matched against is simply the running count of the test within the file. ---debug:: +-d,--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 @@ -89,14 +89,14 @@ appropriately before running "make". failed tests so that you can inspect its contents after the test finished. ---immediate:: +-i,--immediate:: This causes the test to immediately exit upon the first failed test. Cleanup commands requested with test_when_finished are not executed if the test failed, in order to keep the state for inspection by the tester to diagnose the bug. ---long-tests:: +-l,--long-tests:: This causes additional long-running tests to be run (where available), for more exhaustive testing.
-- 1.7.9