NAMING 1.07 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Test sources should be named:

  t????-function.c

where ???? is a four digit code.  The first two digits classify
the test into a major category; the final two digits indicate the
sequence of the test within that category.  The function part of
the test name should give a rough indication of what it does.

Categories
----------

00__: Core library routines based only on the standard library,
      and that are essential for everything else to run.  E.g.
      errno and malloc.

01__: Basic hashing functions, needed to handle the content
      addressable store.

02__: Basic object read access.
Ramsay Jones committed
21 22

03__: Basic object writing.
23 24

04__: Parsing and loading commit data
25

26
05__: Revision walking
27

28
06__: Index reading, writing and searching
29

30
07__: Tests for the internal hashtable code
31

32
08__: Tag reading and writing
33

34
09__: Reading tree objects
35

36 37 38 39 40 41 42 43
10__: Symbolic, loose and packed references reading and writing.

11__: SQLite backend

12__: Repository init and opening

13__: Threads, empty as of now

Vicent Marti committed
44 45 46
14__: Redis backend

15__: Configuration parsing
Jason Penny committed
47 48 49 50

16__: Remotes

17__: Buffers
51 52

18__: File Status