shibboleth-dev - Re: unit test log
Subject: Shibboleth Developers
List archive
- From: Tom Scavo <>
- To:
- Subject: Re: unit test log
- Date: Fri, 26 Aug 2005 17:08:43 -0400
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=beCCJwW8ggML/phCeosgPh3JyKoxNR2lQIy3h96UQ62fx6Gt3GCbWGA/yyMNl4+2EP7IrK/Qonhaq4KKO1xF23Bu3bM/SsqwKtT5QOF5u/0VZTq+vqBxzVPinpUGIs2JPWPBYQoHCeSFbg9X2OpjjJrq2NXKpBQHsi51Vm2NjBM=
On 8/26/05, Walter Hoehn
<>
wrote:
> My
> understanding of junit testing philosophy, though, is that a there
> should be no output from test cases unless there is a failure.
For pre-install unit testing, that makes perfect sense, but for
development work, it sure would be useful to crank up logging to the
hilt. If I change the level in the source to DEBUG and add a
properties file somewhere, will I get output? (Sorry, I don't know
much about log4j.)
Thanks,
Tom
- unit test log, Tom Scavo, 08/22/2005
- Re: unit test log, Walter Hoehn, 08/26/2005
- Re: unit test log, Tom Scavo, 08/26/2005
- Re: unit test log, Walter Hoehn, 08/26/2005
- Re: unit test log, Tom Scavo, 08/26/2005
- <Possible follow-up(s)>
- RE: unit test log, Wilcox, Mark, 08/26/2005
- Re: unit test log, Walter Hoehn, 08/26/2005
Archive powered by MHonArc 2.6.16.