[Octave-bug-tracker] [bug #51708] multiple --eval options results in corrupted parsing of command line

[Mike Miller]

Follow-up Comment #8, bug #51708 (project octave):

Automake includes basic support for running series of test scripts or programs
and collecting the exit statuses, that's the test framework I've used mostly
with autotools in the past.

Autoconf includes Autotest, but that's just another m4-based macro language
like Autoconf for building portable test scripts, seems like overkill for what
we need.

Dejagnu seems to still be around, I've never used it.

I think most of the more fully-featured testing frameworks are going to be
huge libraries built on perl, python, ruby, node, etc, and we probably don't
want to add that bloat just to run some command-line permutations of the
octave executable. I would lean towards just using Automake's built-in
mechanism for running scripts.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51708>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/