#1 usage errors are silent
Closed: Fixed 2 years ago Opened 3 years ago by netvor.

Most internal funcions call __jat__usage() on usage errors, but this does not emit ERROR event. This means that usage errors will pass unnoticed.

To reproduce:

jat__pstartt
    jat__cmp one definitely_invalid_op two
jat__pend

the above will show error on console using warn() from pretty.sh, but log will simply not contain the event at all, implying that the test passed.


First possible solutions that come to mind:

  • kill the test,
  • emit ERROR event (but inherit caseid?)

Login to comment on this ticket.

Metadata