[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #38776] Tests in private functions cannot be t
From: |
Thomas Weber |
Subject: |
[Octave-bug-tracker] [bug #38776] Tests in private functions cannot be tested directly |
Date: |
Tue, 11 Jun 2013 20:50:21 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.31 (KHTML, like Gecko) Chrome/26.0.1410.43 Safari/537.31 |
Follow-up Comment #1, bug #38776 (project octave):
I disagree with the rationale provided here.
Why do we advise users to run "make check"? Because it ensures that
compilation was successful and Octave will run as expected.
So, if you include tests in a file, you want those tests to be run after the
build, such that problems are found NOW and not at some arbitrary point in the
future (if at all).
As such, every test should be run at build time - it does not matter where it
is (if the test is known to fail, that's what xtest is for).
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?38776>
_______________________________________________
Nachricht gesendet von/durch Savannah
http://savannah.gnu.org/
- [Octave-bug-tracker] [bug #38776] Tests in private functions cannot be tested directly,
Thomas Weber <=