[Octave-bug-tracker] [bug #42150] [N, MAX] = test(...) always returns [0, 0] if a test fails

[Mike Miller]

Update of bug #42150 (project octave):

                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #1:

Thanks for the report. I think you do misunderstand though. The first
paragraph of the help for test says:

> the tests are run interactively and stop
> after the first error is encountered.

It doesn't explicitly say this, but the return values seem to always be zero
if the test function is not run in "batch" mode, meaning you have given it a
file descriptor as the third argument. But since test stops on the first
failing test, there's no point in reporting the number of tests passed or the
total number, since it may not have run all of them.

If you want to run all tests in a function, try


octave:1> [n, max] = test ("myfunc", [], stdout)


It's a little clunky, but that forces it into batch mode and runs all tests,
not stopping at the first failure. Does that do what you want?

    _______________________________________________________

Reply to this item at:

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

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