Hi all, My first attempt to send the first version of the files failed. See below the text: ---------- Forwarded message ---------- From: Hélio Guilherme <helioxentric(a)gmail.com&gt; Date: Mon, Apr 11, 2016 at 1:26 AM Subject: Re: [Gretl-devel] Proposal for creation of Unit and Acceptance Tests To: Gretl development <gretl-devel(a)lists.wfu.edu&gt; Hi All, This is my first adaptation of Allin's test package. This setup still must be done/checked. Path to gretl and libgretl. After this, it should be fine for any (Linux) user. The test-gretl.zip (17MB) is (deleted URL: // drive.google.com/open?id=0Bx8T-KbkRZold0pkTW1rMDZBZG8) Attached is a diff of my files vs Allin's. I also attached here analysis of 2016a and development versions against the original tests from Allin's package. All these files are at this folder (deleted URL: // drive.google.com/folderview?id=0Bx8T-KbkRZolWFE5MWxGNm5LLUU&usp=sharing) (There are obvious differences in R and Octave because of missing libraries, and missing files, and applications) My system is Linux CentOS 7. I don't know if the "baseline" outputs do match the released 2016a (I suspect not). These are the changes I have done: Force running Gretl in English. After Gretl "newout" has been created those files are edited, so that all user ($HOME and test-gretl) paths are replaced to simulate "output" original files. TODO: Remove inconsistent paths, on Allin's original "output" files preparation (make new). Try to not compare with "output", when applications are not installed (Stata, OX, ...) Obtain system info (kind of benchmarking, or performance factoring) Should we also do the NIST tests? There is a test that creates two Gnuplot plots, maybe they should have output to PNG. When I tested in Portuguese, there were warnings on strings max length (need tests for all languages). ---- EOT ---- I have now created a GitHub project to keep the test files. Everyone may clone the directory gretl-tests/test-gretl (which are Allin's tests adapted to your own machines). After this first testing fixes, I will prepare automation system and reporting of the test runs. But first we must ensure that there are no missing scripts or data file, and no run when applications are not installed (like stata in my case). There are 902 gretl scripts and in my setup the all_fails file contains 36 failed, and from these, there are 9 caused by missing gretl scripts (other because missing stata, numeric or spacing differences). Better analysis will follow after solving easy fails. The git repository is at: https://github.com/HelioGuilherme66/gretl.git There is a gretl-git project which is a clone from sourceforge (It is not accessible, because it should be independent). Attached are some old test files, but you should see latest_tests.zip <https://github.com/HelioGuilherme66/gretl/blob/master/gretl-tests/test-gr... . I expect to receive Pull Requests with the adding of missing data/scripts files. I am willing to give Collaborator access to the owners of Gretl and major contributors :) Now that we have a GitHub base, we can think in having Gitter or Slack, for instant messaging (I love Slack ;). Have fun :)