[Ecls-list] Testing re-organisation

[Roger Sen Montero]

Daniel,

Just not to duplicate effort, what do you have in mind for the testing part
of ecl? Currently tests are downloaded from Sourceforge (and are not part
of the distribution), the makefile used is less than optimal and the output
of the results is difficult to manipulate.

 So what is the plan for the test files? I see three possible options:

 1) Include them in the main distribution/git repository.

 PROs: no external dependencies.
 CONs: bigger source tar.gz. // test linked to downloaded ecl version.

 2) Include them in a secondary git repository and do a git clone before
running the tests.

 PROs: being able to update tests for all existing ecl versions. // we
don't increase .tar.gz
 CONs: dependency with git.

 3) Move the tests to a secondary git lab repo and download as we do it
today but from the .tar.gz in gitlab.

 PROs: being able to update tests for all existing ecl versions. // we
don't increase .tar.gz
 CONs: maybe some kind of bandwidth limit with gitlab?

 Also there's the need to update tests/Makefile, but this is a trivial
tasks.

 Comments? I'm happy to create a branch and do this changes.

-- 
Roger Sen Montero
roger.sen at gmail.com
+34 649 975 570
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20150406/01e6d344/attachment.html>