[15556] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: New Python test framework

daemon@ATHENA.MIT.EDU (Ezra Peisach)
Fri Mar 5 00:10:35 2010

Message-ID: <4B909244.1050400@mit.edu>
Date: Fri, 05 Mar 2010 00:10:28 -0500
From: Ezra Peisach <epeisach@mit.edu>
MIME-Version: 1.0
To: Greg Hudson <ghudson@mit.edu>
In-Reply-To: <1267762607.18898.131.camel@ray>
Cc: "krbdev@mit.edu" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu

On 3/4/2010 11:16 PM, Greg Hudson wrote:
> On Thu, 2010-03-04 at 22:01 -0500, Ezra Peisach wrote:
>    
>> 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?
>>      
> Hm, perhaps.  I was mostly trying to cut down on output clutter by
> making successful tests silent, but a little bit of output wouldn't be a
> terrible thing.
>
>    
>> b) Failure of a test does not stop the test suite
>>      
> That's a mistake.  I wanted it to be like the t_whatever C programs
> where the test suite would just stop when one of them failed.  I'll fix
> it.
>
>
>    
Perhaps on (a) - success takes an argument that is not displayed unless 
a verbose flag is set...

Ezra

_______________________________________________
krbdev mailing list             krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev

home help back first fref pref prev next nref lref last post