[postgis-tickets] r15357 - Add docs about running regression tests individually

bjorn at wololo.org bjorn at wololo.org
Fri Apr 21 09:38:33 PDT 2017


Author: bjornharrtell
Date: 2017-04-21 09:38:33 -0700 (Fri, 21 Apr 2017)
New Revision: 15357

Modified:
   trunk/regress/README
Log:
Add docs about running regression tests individually

Modified: trunk/regress/README
===================================================================
--- trunk/regress/README	2017-04-21 16:32:26 UTC (rev 15356)
+++ trunk/regress/README	2017-04-21 16:38:33 UTC (rev 15357)
@@ -24,9 +24,9 @@
 ----------------------------
 
 1. Write a /regress/<testname>.sql file with data and sql queries for testing
-2. Write a /regress/<testname>_expected or <testname>_expected.in file with 
+2. Write a /regress/<testname>_expected or <testname>_expected.in file with
    expected results per query
-   The expected results provided in the <testname>_expected file must be 
+   The expected results provided in the <testname>_expected file must be
    formatted using the following psql options:
       -a -- unaligned columns
       -f | -- use | (pipe) as the field separator between columns
@@ -74,9 +74,18 @@
 
   #include "../postgis_config.h"
 
-The ability to run a c preprocessor over the expected results prior to 
+The ability to run a c preprocessor over the expected results prior to
 regression testing was needed for testing curved string functionality that
 would elicit different responses from JTS vs GEOS compilations.  Since
 JTS is no longer supported, this may not be required anymore.
 
 
+Notes about running individual regression tests
+-----------------------------------------------
+
+The script regress/run_test.pl can called directly to run individual
+regression tests. Run it without parameters for info about its usage.
+
+But it should be noted that tests run in a staged install that require
+running make -C regress/ staged-install to actually use the current
+local build. This is called automatically when using make test.



More information about the postgis-tickets mailing list