Some guidelines on how the JBoss org would like the JUnit tests structured
would also be helpful for those of us that would like to add more JUnit
tests to the suite.
I few months ago I was playing with xmlBlaster (www.xmlblaster.org). I
liked how they used JUnit to test their code. Their process wasn't perfect
but there was some uniformity in how tests were submitted to the group and
each test was easy to run (You could also run the entire suite of tests at
once).
Just a suggestion, and thanks for your efforts.
Brett
>From: Peter Braswell <[EMAIL PROTECTED]>
>Reply-To: "jBoss Developer" <[EMAIL PROTECTED]>
>To: jBoss Developer <[EMAIL PROTECTED]>
>Subject: Re: [jBoss-Dev] Writing tests
>Date: Wed, 7 Feb 2001 04:52:34 -0800 (PST)
>
>Hi Toby,
>
>jbosstest is a bit of a hodge-podge. Let me try to
>sort it out a bit.
>
>The the core of this CVS module is the CTS stuff. CTS
>is the conformity test suite. I haven't done much
>documentation for this yet, but I will... I promise!
>
>CTS is based heavily on JUnit which is a testing
>framework. You asked for a pattern and in the context
>of CTS the JUnit framework is it.
>
>As far as the other test in jbosstest, they are the
>contributions of the contributors to JBOSS. They are
>adhoc and do not necessarily conform to an particular
>standard, but more the style of an individual
>developer. They in turn test individual pieces of
>code or functionality that were coded by a
>developer/contributor, many having been developed
>prior to adopting JUnit as a testing framework.
>
>Does this help? I can provide further clarification
>if needed.
>
>cheers,
>peter
>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
