Test name policy in place

rurban · Mar 28, 2012 · efbae83 · efbae83
1 parent 2fb9664
commit efbae83
Show file tree

Hide file tree

Showing 6 changed files with 23 additions and 0 deletions.
diff --git a/t/00-load.t → t/000-load.t b/t/00-load.t → t/000-load.t
diff --git a/t/100-new-and-destroy.t → t/010-new-and-destroy.t b/t/100-new-and-destroy.t → t/010-new-and-destroy.t
diff --git a/t/101-include.t → t/011-include.t b/t/101-include.t → t/011-include.t
diff --git a/t/102-define.t → t/012-define.t b/t/102-define.t → t/012-define.t
diff --git a/t/103-code-setters.t → t/013-code-setters.t b/t/103-code-setters.t → t/013-code-setters.t
diff --git a/t/README b/t/README
@@ -0,0 +1,23 @@
+The test files are ordered thus:
+
+0** - basic and non-compile-based tests
+1** - compile-based tests
+2** - Perl package tests
+3** - other package tests
+4** - tests of other functionality
+
+0-level tests do not require any sort of compilation or interaction with the
+compiled code. They look like normal Perl tests.
+
+100-level tests require interaction with compiled code, but cannot invoke any
+packages. Since TCC::Perl is a package, this means that the only interaction
+is via printing to stdout. As such, all 100-level tests invoke code that
+communicates via C printf's, and use inc::Capture to get the results.
+
+200-level tests focus exclusively on the TCC::Perl package.
+
+300-level tests focus on the other included packages. They can interact with
+the perl interpreter via TCC::Perl, since that will already have been
+tested by the time these run.
+
+400-level tests are for other submodules of the library.