[8261] tp/t/README

[gavinsmith0123]

Revision: 8261
          http://svn.sv.gnu.org/viewvc/?view=rev&root=texinfo&revision=8261
Author:   gavin
Date:     2018-10-06 04:38:16 -0400 (Sat, 06 Oct 2018)
Log Message:
-----------
tp/t/README

Modified Paths:
--------------
    trunk/ChangeLog
    trunk/tp/t/README

Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog     2018-10-06 08:25:56 UTC (rev 8260)
+++ trunk/ChangeLog     2018-10-06 08:38:16 UTC (rev 8261)
@@ -1,3 +1,7 @@
+2018-10-06  Gavin Smith  <address@hidden>
+
+       * tp/t/README: Add more advice.
+
 2018-09-30  Gavin Smith  <address@hidden>
 
        * tp/test_utils.pl: Set 'TEST' to 1 for converters.

Modified: trunk/tp/t/README
===================================================================
--- trunk/tp/t/README   2018-10-06 08:25:56 UTC (rev 8260)
+++ trunk/tp/t/README   2018-10-06 08:38:16 UTC (rev 8261)
@@ -41,6 +41,10 @@
 (Any number at the start of the name of the test, like "03" in this
 example, is removed.)
 
+When making changes that you expect will change the parse tree but not 
+change any of the output, one way to check this would be to run "make 
+check" and then "grep FAIL test-suite.log | grep -v 'tree$'".
+
 Another way to check test results is to regenerate the reference test 
 results (see below), and then run "svn diff t".
 
@@ -64,6 +68,7 @@
 subdirectory.  When adding a test that uses an input file, add its path 
 to tp/Makefile.am.
 
+
 For some tests, as well as a .pl file as usual in results/*/, actual
 output files are generated.  For those tests, there are directories with
 reference test results (with names prefixed with res_), and directories
@@ -78,6 +83,11 @@
 "./maintain/all_tests.sh diff" makes a diff of all resulting files
 against references.
 
+Another way to overwrite the reference test results with the obtained 
+results from the last test run is to use a command like
+
+  for f in t/results/*/*.pl.new ; do cp ${f%.new} $f ; done
+
 From the top directory, you can also create texinfo files corresponding to
 tests by running something along the lines of: