octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #61199] Allow 'char' input sets to nchoosek fo


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #61199] Allow 'char' input sets to nchoosek for Matlab compatibility
Date: Thu, 23 Sep 2021 22:54:59 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Follow-up Comment #18, bug #61199 (project octave):

Yeah, we should probably document the preferred style for writing tests.

%!xtest came before the idea of adding bug report numbers to the tests.  Now
that tests can be tagged with bug numbers, I think %!xtest is mostly
obsolete.

You can use


%!test <NNNNNN>
%!  additional test lines
%!  are usually indented

%!assert <NNNNNN> (condition)
%!assert <NNNNNN> (test_expr, expected_result)


Note that using "%!  assert (...)" in a multi-line test block is just a call
to the assert function and is not the same as "%!assert", so you can't use a
bug number there.

Prefixing a bug number with "*" (i.e., "<*123456>" indicates that the bug
status is "fixed", so any failure will be reported as a regression, not a
known bug.  The "update-bug-status" target in the Makefile will search for
tests with numbers, get the status from the bug tracker, and then edit the
sources to add the "*" if needed.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?61199>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]