1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
|
# Testing
## Testing Prolog standards compliance
Using the latest git versions of both Tau Prolog and Logtalk, is now possible
to use Logtalk's Prolog compliance test suite to check Tau Prolog. Tests can
be run automated or manually.
Assuming a POSIX system, follow this [guide](https://logtalk.org/running_developer_versions.html)
to install the Logtalk git version, which includes a `taulgt.sh`
integration script (for details, use `man taulgt`). This script
requires that the `NODE_PATH` environment variable be set to the
`node_modules` directory path where Tau Prolog and its dependencies
are installed:
```bash
$ ll $NODE_PATH
total 0
drwxr-xr-x 7 johndoe staff 224 May 21 09:42 balanced-match
drwxr-xr-x 6 johndoe staff 192 May 21 09:42 brace-expansion
drwxr-xr-x 8 johndoe staff 256 May 21 09:42 commander
drwxr-xr-x 9 johndoe staff 288 May 21 09:42 concat-map
drwxr-xr-x 17 johndoe staff 544 May 21 09:42 js-reporters
drwxr-xr-x 6 johndoe staff 192 May 21 09:42 minimatch
drwxr-xr-x 10 johndoe staff 320 May 21 09:42 node-watch
drwxr-xr-x 8 johndoe staff 256 May 21 09:42 path-parse
drwxr-xr-x 9 johndoe staff 288 May 21 09:42 qunit
drwxr-xr-x 7 johndoe staff 224 May 21 09:42 readline-sync
drwxr-xr-x 16 johndoe staff 512 May 21 09:42 resolve
drwxr-xr-x 9 johndoe staff 288 May 21 09:42 tau-prolog
```
For good performance when testing, edit the `$LOGTALKHOME/core/core.pl`
file to turn off the `clean` flag. Search for the definition of the
predicate `'$lgt_load_built_in_entity'/4` (near the end of the file)
and change `clean(on)` to `clean(off)`.
Next, test the setup by running the `taulgt.sh` integration script.
First run will be slow but you should get the default Logtalk startup
messages that include a banner and a list of the default flag values
followed by tips on developer tools. Something like:
```text
$ taulgt.sh
Logtalk 3.46.0
Copyright (c) 1998-2021 Paulo Moura
% Default lint compilation flags:
% unknown_predicates: warning, undefined_predicates: warning
...
% For Logtalk compiler warnings/errors explanations and fix suggestions, use:
% ?- {tutor(loader)}. or ?- logtalk_load(tutor(loader)).
%
?-
```
For the actual testing, change the current directory to one of the
leaf sub-directories of the `$LOGTALKHOME/tests/prolog` directory.
For example:
```text
$ cd $LOGTALKHOME/tests/prolog/predicates/term_variables_2
$ taulgt.sh
?- {tester}.
```
The first time a test set is run, it will be slow. But thanks to
the setting of the `clean` flag to `off`, subsequent runs will be
much faster as they will use the pre-compiled libraries and tools
from the first run.
To run tests automatically, change to the intended directory and use the
`logtalk_tester.sh` script. For example:
```text
$ cd $LOGTALKHOME/tests/prolog/
$ logtalk_tester.sh -p tau -g "set_logtalk_flag(clean,off)" -w
...
```
When you get a failed test, check the Tau Prolog current open issues
before reporting it. Note that different failed tests may have a common
cause. Also, keep in mind that standards compliance is hard work.
Prioritize your bug reports. For example, failed tests due to an
exception being different from the one specified by the standards are
likely not as important at this point as failed tests where a goal
that is expected to succeed fails or a goal that is expected to fail
succeeds. For the actual goal of a failed test, use the test identifier
to locate the test in the `tests.lgt` file in the directory.
This guide will be updated for Tau Prolog standards compliance progress
and for improved Logtalk support for Tau Prolog. Do a `git pull` on both
your Tau Prolog and Logtalk git clones before running any tests to ensure
that you will be testing the current versions.
|
