harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Blewitt" <alex.blew...@gmail.com>
Subject Re: Re: [classlib] Testing conventions - a proposal
Date Mon, 10 Jul 2006 20:47:18 GMT
On 10/07/06, Alexei Zakharov <alexei.zakharov@gmail.com> wrote:
> Hi George,
> > For the purposes of this discussion it would be fascinating to find out
> > why you refer to TestNG as being an "unstable" test harness. What is
> > that statement based on ?
> My exact statement was referring to TestNG as "probably unstable"
> rather than simply "unstable". ;)  This statement was based on posts
> from Richard Liang about the bug in the TestNG migration tool and on
> common sense. If the project has such an obvious bug in one place it
> may probably have other bugs in other places. JUnit is quite famous
> and widely used toolkit that proved to be stable enough. TestNG is
> neither famous nor widely used.

Unfortunately, this isn't terribly correct :-) The purpose of the
JUnit migration tool is to automatically add annotations to an
existing source, and is independent from the test harness itself.
TestNG is also quite famous, and indeed, a lot of what's available in
JUnit4 was based on ideas from TestNG. It's also been around since
August 2004, so it's had almost a couple of years out in the field
(and as the download page [1] shows, it's pretty active). There's also
plugins for any build system you care to name (ant, maven, Eclipse,
IntelliJ) and it's pretty widely adopted in certain areas.

In short, not a terribly common-sense post :-)


[1] http://testng.org/doc/download.html

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org

View raw message