| 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. |
| |
| 03__: Basic object writing. |
| |
| 04__: Parsing and loading commit data |
| |
| 05__: Revision walking |
| |
| 06__: Index reading, writing and searching |
| |
| 07__: Tests for the internal hashtable code |
| |
| 08__: Tag reading and writing |
| |
| 09__: Reading tree objects |
| |
| 10__: Symbolic, loose and packed references reading and writing. |
| |
| 11__: SQLite backend |
| |
| 12__: Repository init and opening |
| |
| 13__: Threads, empty as of now |
| |
| 14__: Redis backend |
| |
| 15__: Configuration parsing |
| |
| 16__: Remotes |
| |
| 17__: Buffers |
| |
| 18__: File Status |