URL:
<https://savannah.gnu.org/bugs/?62478>
Summary: Make test files testable everywhere
Project: GNU troff
Submitted by: bjarniig
Submitted on: Tue 17 May 2022 02:06:41 AM UTC
Category: General
Severity: 3 - Normal
Item Group: Test
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Discussion Lock: Any
Planned Release: None
_______________________________________________________
Details:
Subject: make test files testable everywhere
Tests, that produce FAIL or SKIP, should be fit to be analysed by the
users anywhere they like, the simplest case in the same directory as
the file resides.
For that the first two body lines should be
cd $abs_top_builddir
<local command name>=./<command name in the build directory>
In the output with FAIL or SKIP status,
the users should get instructions to define an environmental variable
"abs_top_builddir" to be the path to their groff build directory,
and then issue the command:
"sh -x <test file>" (with a redirection)
to see how the test was executed.
There is already a file,
src/devices/grotty/tests/basic_latin_glyphs_map_correctly.sh,
that can profit from this.
Could also help with bug #62357 as it shows there a failure of this
file.
N.B.
No test file should produce the XFAIL or SKIP case except
a) the groff code still has a bug (excluding the test file)
b) the complete operation system does not provide the absolute
necessary resources
The above mentioned test file has a bug, #61891 (closed)
N.B.
This is the simplest version as only files in and below the build
directory are searched for.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62478>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
