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

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

[Octave-bug-tracker] [bug #55522] Add failure summary to __run_test_suit


From: Kai Torben Ohlhus
Subject: [Octave-bug-tracker] [bug #55522] Add failure summary to __run_test_suite__ output?
Date: Tue, 22 Jan 2019 03:21:03 -0500 (EST)
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36

Follow-up Comment #2, bug #55522 (project octave):

Thanks for your contribution. It is indeed a good idea to get faster feedback
about failing tests, than scrolling back or looking at fntests.log.

In your changesets you introduce a new classdef:


scripts/testfun/+octave/+test/+internal/TestSuiteResult


Although it destroys creativity.  I think if we want to overhaul Octave's
testing framework, we should look early at Matlab:
https://www.mathworks.com/help/matlab/class-based-unit-tests.html
Otherwise we later have the pain to become Matlab compatible and remove
duplication.

There is already something similar (not 100% of course) to your
"TestSuiteResult" class. And Octave 5.0 has introduced the "+matlab"
namespace.  So maybe you can try to implement and make use of


matlab.unittest.TestResult
scripts/+matlab/+unittest/TestResult


https://www.mathworks.com/help/matlab/ref/matlab.unittest.testresult-class.html
to get this overview done?

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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