blob: 77f0b6cf63e498291aac9b83bb2afb4165eea650 [file] [log] [blame]
Core GIT Tests
This directory holds many test scripts for core GIT tools. The
first part of this short document describes how to run the tests
and read their output.
When fixing the tools or adding enhancements, you are strongly
encouraged to add tests in this directory to cover what you are
trying to fix or enhance. The later part of this short document
describes how your test scripts should be organized.
The mechanism that powers this testsuite is directly imported from the
Core GIT Tests, in directory t/ of the git repository. Files are base
on Core GIT version 1.3.0.rc4.g5069.
Running Tests
The easiest way to run tests is to say "make -C t". This runs all
the tests.
*** ***
* ok 1: .git/objects should be empty after git-init-db in an empty repo.
* ok 2: .git/objects should have 256 subdirectories.
* ok 3: git-update-index without --add should fail adding.
* ok 23: no diff after checkout and git-update-index --refresh.
* passed all 23 test(s)
*** ***
* ok 1: using old names should issue warnings.
* ok 2: using old names but having new names should not issue warnings.
Or you can run each test individually from command line, like
$ sh ./
* ok 1: git-update-index --add to add various paths.
* ok 2: git-ls-files -k to show killed files.
* ok 3: validate git-ls-files -k output.
* passed all 3 test(s)
You can pass --verbose (or -v), --debug (or -d), and --immediate
(or -i) command line argument to the test.
This makes the test more verbose. Specifically, the
command being run and their output if any are also
This may help the person who is developing a new test.
It causes the command defined with test_debug to run.
This causes the test to immediately exit upon the first
failed test.
Naming Tests
The test files are named as:
where N is a decimal digit.
Here is a proposal for numbering, loosely based on the Core GIT
numbering conventions.
First two digit tells the particular command we are testing:
00 - stgit itself
10 - branch
11 - clone
12 - push
Third and fourth digit (optionally) tells the particular switch or
group of switches 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
especially needed if you are creating a common test library
file, similar to, because such a library file may
not be suitable for standalone execution.
Writing Tests
The test script is written as a shell script. It should start
with the standard "#!/bin/sh" with copyright notices, and an
assignment to variable 'test_description', like this:
# Copyright (c) 2005 Junio C Hamano
test_description='xxx test (option --frotz)
This test registers the following structure in the cache
and tries to run git-ls-files with option --frotz.'
Source ''
After assigning test_description, the test script should source like this:
. ./
This test harness library does the following things:
- If the script is invoked with command line argument --help
(or -h), it shows the test_description and exits.
- Creates an empty test directory with an empty .git/objects
database and chdir(2) into it. This directory is 't/trash'
if you must know, but I do not think you care.
- Defines standard test helper functions for your scripts to
use. These functions are designed to make all scripts behave
consistently when command line arguments --verbose (or -v),
--debug (or -d), and --immediate (or -i) is given.
End with test_done
Your script will be a sequence of tests, using helper functions
from the test harness library. At the end of the script, call
Test harness library
There are a handful helper functions defined in the test harness
library for your script to use.
- test_expect_success <message> <script>
This takes two strings as parameter, and evaluates the
<script>. If it yields success, test is considered
successful. <message> should state what it is testing.
test_expect_success \
'git-write-tree should be able to write an empty tree.' \
- test_expect_failure <message> <script>
This is the opposite of test_expect_success. If <script>
yields success, test is considered a failure.
This should _not_ be used for tests that succeed when their
commands fail -- use test_expect_success and shell negation (!) for
that. test_expect_failure is for cases when a test is known to be
- test_debug <script>
This takes a single argument, <script>, and evaluates it only
when the test script is started with --debug command line
argument. This is primarily meant for use during the
development of a new test script.
- test_done
Your test script must have test_done at the end. Its purpose
is to summarize successes and failures in the test script and
exit with an appropriate error code.
Tips for Writing Tests
As with any programming projects, existing programs are the best
source of the information. However, do _not_ emulate when writing your tests. The test is special in
that it tries to validate the very core of GIT. For example, it
knows that there will be 256 subdirectories under .git/objects/,
and it knows that the object ID of an empty tree is a certain
40-byte string. This is deliberately done so in
because the things the very basic core test tries to achieve is
to serve as a basis for people who are changing the GIT internal
drastically. For these people, after making certain changes,
not seeing failures from the basic test _is_ a failure. And
such drastic changes to the core GIT that even changes these
otherwise supposedly stable object IDs should be accompanied by
an update to
However, other tests that simply rely on basic parts of the core
GIT working properly should not have that level of intimate
knowledge of the core GIT internals. If all the test scripts
hardcoded the object IDs like does, that defeats
the purpose of, which is to isolate that level of
validation in one place. Your test also ends up needing
updating when such a change to the internal happens, so do _not_
do it and leave the low level of validation to