texinfo-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[6648] partial tp tests update


From: Gavin D. Smith
Subject: [6648] partial tp tests update
Date: Sun, 27 Sep 2015 11:30:51 +0000

Revision: 6648
          http://svn.sv.gnu.org/viewvc/?view=rev&root=texinfo&revision=6648
Author:   gavin
Date:     2015-09-27 11:30:49 +0000 (Sun, 27 Sep 2015)
Log Message:
-----------
partial tp tests update

Modified Paths:
--------------
    trunk/ChangeLog
    trunk/tp/t/README
    trunk/tp/tests/README
    trunk/tp/tests/layout/res_parser/formatting_regions/formatting_regions.2

Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog     2015-09-25 16:30:28 UTC (rev 6647)
+++ trunk/ChangeLog     2015-09-27 11:30:49 UTC (rev 6648)
@@ -1,3 +1,16 @@
+2015-09-27  Gavin Smith  <address@hidden>
+
+       * tp/t/README: Mention tests under tp/tests.  Remove "texinfo/" 
+       from start of a path.
+       * tp/tests/README: Change a word "one" to "a".  Add headings
+       "Regenerating test results" and "Checking test results".  Add an 
+       example to show how to investigate a test failure.  Change 
+       "content" to "contents" and "files" to "file", and "line 
+       oriented" to "line-oriented".
+
+       * tp/t/tests/test_scripts/layout_formatting_regions.sh: Update 
+       results for this "long-checks" test (more to come).
+
 2015-09-25  Gavin Smith  <address@hidden>
 
        * info/session.c (incremental_search)

Modified: trunk/tp/t/README
===================================================================
--- trunk/tp/t/README   2015-09-25 16:30:28 UTC (rev 6647)
+++ trunk/tp/t/README   2015-09-27 11:30:49 UTC (rev 6648)
@@ -8,10 +8,12 @@
   modification, are permitted in any medium without royalty provided the
   copyright notice and this notice are preserved.
 
-Files anywhere within the texinfo/tp/t/ subdirectory which have no
+Files anywhere within the tp/t subdirectory which have no
 other copyright notice are hereby placed in the public domain.
 
+See also the tests in the tp/tests directory.
 
+
 These tests are run by "make check" under tp/.  (The test files are 
 listed in tp/Makefile.tres, which is a generated file.)  A single .t 
 test file can be run on its own with

Modified: trunk/tp/tests/README
===================================================================
--- trunk/tp/tests/README       2015-09-25 16:30:28 UTC (rev 6647)
+++ trunk/tp/tests/README       2015-09-27 11:30:49 UTC (rev 6648)
@@ -32,15 +32,17 @@
 * Using ./parser_tests.sh with the directories one want to run the tests 
 in given as arguments
 
-* By going into one directory and running ../run_parser_all.sh, like
+* By going into a directory and running ../run_parser_all.sh, like
 $ cd formatting
 $ ../run_parser_all.sh
 
-* By going into one directory and running one specific test, like
+* By going into a directory and running one specific test, like
 $ cd formatting
 $ ../run_parser_all.sh cond
 (see below for info on how test names are specified).
 
+Checking test results
+---------------------
 The test results are in the out_parser directories; the reference
 results are in res_parser directories.  There can be these pairs.
 - out_parser/ and res_parser/ for html output in texi2html style;
@@ -48,11 +50,26 @@
 - out_parser_info/ and res_parser_info/ for info results;
 and diffs are put in the diffs/ subdir.
 
-If a test failed when run via parser_tests.sh or run_parser_all.sh, then
- F: a_test_directory 
-is printed, if there is a diff with the references, a
+For example, to investigate a failure in the 
+test_scripts/layout_formaatting_docbook.sh test, compare the contents of the
+files in the layout_res_parser/formatting_docbook and 
+layout_out_parser/formatting_docbook directories, e.g.
+
+diff {res,out}_parser/formatting_docbook/formatting.2
+
+Also look in the layout/diffs directory.
+
+If the test results are as expected, copy the output files onto the 
+reference files.  Otherwise, if they need more investigation, see "Tests 
+specification" below, to find out what input file, etc. was used for the 
+test.
+
+When running tests via parser_tests.sh or run_parser_all.sh, then
+a test failure causes
+ F: a_test_directory
+to be printed.  If there is a diff with the references, then
  D: a_test_directory
-is printed. If there are no reference to compare with, 
+is printed. If there are no reference to compare with, then
  no res: a_test_directory
 is printed.
 
@@ -67,6 +84,9 @@
 out_parser/a_test/a_test.1.  All the commands called are output in 
 tests.log.
 
+Regenerating test results
+=========================
+
 Giving -copy as the first argument to ../run_parser_all.sh or
 parser_tests.sh (or long_tests.sh or tex_html_tests.sh, which need
 environment variables LONG_TESTS resp. TEX_HTML_TESTS, or ALL_TESTS, to
@@ -85,7 +105,7 @@
 
 
 TeX4ht and LaTeX2HTML tests
----------------------------
+===========================
 The tex4ht and latex2HTML related tests are not run automatically, as
 some test results involving latex2HTML or tex4ht depend on the setup and 
 version of these tools.
@@ -100,8 +120,8 @@
 
 Tests specification
 ===================
-Test runs are driven by the content of the tests-parser.txt files in
-each subdirectory. This is a line oriented file. A # starts a
+Test runs are driven by the contents of the tests-parser.txt file in
+each subdirectory. This is a line-oriented file. A # starts a
 comment, except that the very first line of the file can be, e.g.,
 # formats :html
 which says which formats to generate.

Modified: 
trunk/tp/tests/layout/res_parser/formatting_regions/formatting_regions.2
===================================================================
--- trunk/tp/tests/layout/res_parser/formatting_regions/formatting_regions.2    
2015-09-25 16:30:28 UTC (rev 6647)
+++ trunk/tp/tests/layout/res_parser/formatting_regions/formatting_regions.2    
2015-09-27 11:30:49 UTC (rev 6648)
@@ -198,19 +198,6 @@
 formatting_regions.texi:49: @ref reference to nonexistent node `node' 
(possibly involving @mymacro)
 formatting_regions.texi:49: @ref reference to nonexistent node `node' 
(possibly involving @mymacro)
 formatting_regions.texi:49: @ref reference to nonexistent node `node' 
(possibly involving @mymacro)
-formatting_regions.texi:22: warning: unreferenced node `constructs'
-formatting_regions.texi:22: warning: node `chapter' is next for `constructs' 
in sectioning but not in menu
-formatting_regions.texi:22: warning: node `Top' is up for `constructs' in 
sectioning but not in menu
-formatting_regions.texi:8: node `Top' lacks menu item for `constructs' despite 
being its Up target
-formatting_regions.texi:87: warning: unreferenced node `chapter'
-formatting_regions.texi:87: warning: node `chapter2' is next for `chapter' in 
sectioning but not in menu
-formatting_regions.texi:87: warning: node `constructs' is prev for `chapter' 
in sectioning but not in menu
-formatting_regions.texi:87: warning: node `Top' is up for `chapter' in 
sectioning but not in menu
-formatting_regions.texi:8: node `Top' lacks menu item for `chapter' despite 
being its Up target
-formatting_regions.texi:121: warning: unreferenced node `chapter2'
-formatting_regions.texi:121: warning: node `chapter' is prev for `chapter2' in 
sectioning but not in menu
-formatting_regions.texi:121: warning: node `Top' is up for `chapter2' in 
sectioning but not in menu
-formatting_regions.texi:8: node `Top' lacks menu item for `chapter2' despite 
being its Up target
 formatting_regions.texi:28: @verbatiminclude: could not find simplest.texi 
(possibly involving @mymacro)
 formatting_regions.texi:39: warning: @image file `f-ile' (for HTML) not found, 
using `f-ile.jpg' (possibly involving @mymacro)
 formatting_regions.texi:39: warning: @image file address@hidden' (for HTML) 
not found, using address@hidden ext e--xt}' (possibly involving @mymacro)




reply via email to

[Prev in Thread] Current Thread [Next in Thread]