Thank you Allin.

I started to harmonize the test files, and I would like to have a GitHub project for anyone who wants to replicate the tests.
IMPORTANT: Is it OK for me to create this GitHub project (from your test package)?

All the data files should be public, but there are some only in your machine. For now I have identified these:
biptest.inp:open ~/stats/stata/school.gdt
sw.inp:open ~/stats/hamilton/macrodat.rat

Datafiles from ~/stats would go to the current test package dir, "test-gretl".
Default datafiles would be taken from gretl under test detected (in my case it is installed in /usr/local).

I am already faking the new outputs to match your original datafiles and scripts files.

Right now I'm very pressed for time, but I'm putting my test rig at

http://ricardo.ecn.wfu.edu/~cottrell/testing/test-gretl.tar.xz

so anyone can take a look. It exercises almost 20000 scripts; the testing mechanism utilizes "make" and shell scripts. Each directory contains "output" and "newout" subdirectories. The basic idea is that "make" in a given directory will populate the "newout" directory with output files, then run a "diff" on newout vs "output" (besides reporting any failures). So "output" is supposed to contain "known good" results.

You can run everything by typing "make test-all" in the top-level directory. This may take a while; it will produce a composite diff of all new output against all previous output.

Anyone running this on their own system should first go into the "bin" directory (under "test-gretl") and edit the file named "sitevars".

 I'll do changes in a way people would easily test gretl with few setup changes.

Thanks,
Hélio