The JUnit list currently seems to be soliciting suggestions for JUnit 4.
Now might be a good time to point out some of the limitations of the
current implementation.
The *very* low bandwidth mailing list is accessible through:
<http://lists.sourceforge.net/lists/listinfo/junit-devel>
Stuart.
On Wednesday, August 1, 2001, at 04:29 am, Peter Donald wrote:
On Wed, 1 Aug 2001 01:16, Berin Loritsch wrote:
That's the point. It really doesn't require alot of learning--I
converted
the tests for i18n package from JUnit to Testlet--which only forced me to
change the class we extended and the name of one or two methods. All the
tests pretty much functioned as is.
As I mentioned in another thread, the graphical feedback of a red bar is
much easier to catch than trolling through mountains of logs for the
ERROR
events--as the debug entries are necessary to figure out what is going on
in case there is an error.
JUnit is open source, so there is nothing that says we can't change
things.
Convinced ... if someone else was to do the work ;) We should probably
also
put a note on testlet website indicating that it is deprecated in favour
of
junit or something.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-------------------------------------------------------------------------
Stuart Roebuck [EMAIL PROTECTED]
Lead Developer Java, XML, MacOS X, XP, etc.
ADOLOS <http://www.adolos.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
