From: Björn Harrtell Date: Fri, 21 Apr 2017 16:38:33 +0000 (+0000) Subject: Add docs about running regression tests individually X-Git-Tag: 2.4.0alpha~131 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=a1ccc660e184651e403e3289e35c255208b08e70;p=postgis Add docs about running regression tests individually git-svn-id: http://svn.osgeo.org/postgis/trunk@15357 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/regress/README b/regress/README index 5121f864e..817d9998c 100644 --- a/regress/README +++ b/regress/README @@ -24,9 +24,9 @@ How to add a regression test ---------------------------- 1. Write a /regress/.sql file with data and sql queries for testing -2. Write a /regress/_expected or _expected.in file with +2. Write a /regress/_expected or _expected.in file with expected results per query - The expected results provided in the _expected file must be + The expected results provided in the _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 @@ configuration header. #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.