Any thoughts about using Log4j for all client and server side logging for
jbosstest? I think that it would help show problems when running from a
console, so that all bits that get displayed are things to worry about by
default. If you want more detail for a given test or set of tests, then
update the log4j.properties.
To make this work we will probably have to create a common JBossTestCase or
something, that will do the proper log4j setup. A common base class for
test cases might not be a bad idea by its own.
--jason
On Tue, 31 Jul 2001, Scott M Stark wrote:
> I was looking to add a new unit test and was looking at an existing test
> and found that it was not using the junit assert and fail methods. Rather,
> it was simply printing out "FAILED" or the like. This is useless for
> automated unit testing. I don't think this is the norm, but if your adding
> or creating tests they have to report failures to the junit framework using
> the
> assert and fail methods. Dumping an error message to the console won't
> work.
>
>
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
