Skip to content
Browse files

Rename the test cases to run in specific orders

This way we can be fairly certain we run tests of lower-level
parts of the library before we run tests of higher-level more
complex parts.  If there is any problem in a lower-level part
of the library, the earlier test will identify it and stop,
making it easire to troubleshoot the failure.

A rough naming guide has been added for the test suite to
explain the current category structure.

Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
  • Loading branch information...
1 parent 5673434 commit 4260699b37a7a0cc6be231d232d424a858a7d111 @spearce spearce committed Dec 31, 2008
View
20 tests/NAMING
@@ -0,0 +1,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.
View
0 tests/t0000-errno.c → tests/t0001-errno.c
File renamed without changes.
View
0 tests/t0000-hash.c → tests/t0101-hash.c
File renamed without changes.
View
0 tests/t0000-oid.c → tests/t0101-oid.c
File renamed without changes.
View
0 tests/t0000-obj.c → tests/t0102-objtype.c
File renamed without changes.
View
0 tests/t0000-obj-hash.c → tests/t0103-objhash.c
File renamed without changes.
View
0 tests/t0000-read1.c → tests/t0201-readloose.c
File renamed without changes.
View
0 tests/t0000-read2.c → tests/t0202-readloose.c
File renamed without changes.

0 comments on commit 4260699

Please sign in to comment.
Something went wrong with that request. Please try again.