[15554] in Kerberos_V5_Development
Re: New Python test framework
daemon@ATHENA.MIT.EDU (Ezra Peisach)
Thu Mar 4 22:01:12 2010
Message-ID: <4B9073F1.2000906@mit.edu>
Date: Thu, 04 Mar 2010 22:01:05 -0500
From: Ezra Peisach <epeisach@mit.edu>
MIME-Version: 1.0
To: krbdev@mit.edu
In-Reply-To: <201003042138.o24LcUtn019715@outgoing.mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
Initial testing reveals the following:
a) It would be nice if success() took an argument that could be
displayed to indicate what the tests were testing... fail() does - and
displays the message... t_general.py might mean something to you now -
but five years from now?
.
b) Failure of a test does not stop the test suite... This might be the
design in which you run all the tests in a directory... If that is the
case, perhaps the for loop under check-python-tests-yes could check the
exit status of a test, but continue running the tests. If at the end -
then exit w/ a non-zero exit status... At least that way if someone does
make check - if something fails they will see it - yet allow for many
tests to take place...
Ezra
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
