On Sun May 20 08:08:13 2007, jkeen <!-- x --> at verizon.net wrote:
> Since I created the postconfigure/ subdirectory, I'll start by  
> writing a patch describing what the tests in that directory are for.   
> If you worked on one of the other 4 undocumented subdirectories,  
> please submit a patch as well.
> 

See patch attached.
Index: t/README
===================================================================
--- t/README    (revision 18590)
+++ t/README    (working copy)
@@ -5,36 +5,39 @@
 For details, see the documentation in '../docs/tests.pod'.
 For status of the testing effort, see 'TESTS.STATUS.pod' in this directory.
 
-benchmark:    Run all benchmarks
+benchmark:      Run all benchmarks
 
-compilers:    Mini languages distributed with Parrot
+compilers:      Mini languages distributed with Parrot
 
-configure:    Perl modules of configuration subsystem
+configure:      Perl modules of configuration subsystem
 
-codingstd:    Conventions and Guidelines for Parrot Source Code
+codingstd:      Conventions and Guidelines for Parrot Source Code
 
-distro:       Tests run before a distro is released
+distro:         Tests run before a distro is released
 
-doc:          Completeness and sanity of the documentation
+doc:            Completeness and sanity of the documentation
 
-dynpmc:       Dynamic PMCs
+dynpmc:         Dynamic PMCs
 
-examples:     Check whether the examples are still working
+examples:       Check whether the examples are still working
 
-library:      Parrot modules
+library:        Parrot modules
 
-native_pbc:   Parrot Byte Code
+native_pbc:     Parrot Byte Code
 
-op:           Try to cover all core operators
+op:             Try to cover all core operators
 
-perl:         Test Perl5 modules used for configuration, building and testing 
of Parrot.
+perl:           Test Perl5 modules used for configuration, building and 
testing of Parrot.
 
-pmc:          Try to cover all builtin PMCs
+pmc:            Try to cover all builtin PMCs
 
-run:          Mostly command line options of the 'parrot' executable
+postconfigure:  Tests of configuration system which cannot be run until
+configuration has completed.
 
-src:          Tests written in C. XXX Is this a meaningful category?
+run:            Mostly command line options of the 'parrot' executable
 
-stress:       Stress testing
+src:            Tests written in C. XXX Is this a meaningful category?
 
-tools:        Executables besides 'parrot'
+stress:         Stress testing
+
+tools:          Executables besides 'parrot'

Reply via email to